2010/10/12 Bruno Randolf <br1@xxxxxxxxxxx>: > Hello! > > I am trying to debug a strange effect, I am seeing on soekris net48xx boards > with two ath5k interfaces: > > Â* wlan0 [phy0] configured in ad-hoc mode, A band, and it is getting a lot of > traffic routed thru it > Â* wlan1 [phy1] also configured in ad-hoc mode, G band, but not actively > sending (no IP address). > > I run iperf between two PCs attached by ethernet, UDP 25Mbps and I am sure all > traffic is routed thru wlan0 (phy0). The load on the SENDING box gets very > high: > > Mem: 27304K used, 99040K free, 0K shrd, 616K buff, 14128K cached > CPU:  0% usr  0% sys  0% nic  0% idle  0% io  5% irq Â93% sirq > Load average: 1.73 1.01 2.23 2/38 3128 > ÂPID ÂPPID USER   STAT  VSZ %MEM %CPU COMMAND > Â2772   2 root   RW    0  0% Â71% [phy1] > Â2757   2 root   SW    0  0% Â11% [phy0] > Â3128  436 root   R   Â988  1%  8% top >  Â3   2 root   SW    0  0%  5% [ksoftirqd/0] >  Â5   2 root   SW    0  0%  3% [events/0] >  56   2 root   SW    0  0%  1% [bdi-default] > Â1383   1 root   S   1824  1%  0% /usr/bin/oprofiled --session-dir=/r > > ...and the interesting thing is that [phy1] - the INACTIVE interface - > consumes much more CPU time than [phy0] which is actually transmitting. > > I have disabled ANI on wlan1, to avoid getting many MIB interrupts, but it > does not change much. > > I have dumped frames on phy1, and all it sees are a few beacon frames. > > I have tried wlan1 in managed mode - same effect. The effect is slightly less > in AP mode, though... > > I tried oprofile, but it shows mostly tx related things. > > So my question is: How can I find out, what [phy1] is so busy doing? Any ideas > how to profile this? > > Thanks in advance, > bruno > When ph1 is also connected consumes more or less CPU ? What happens If you just give it an IP address ? -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick -- 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
