> On Saturday 20 March 2010 11:44:24 Bruno Randolf wrote: >> i think i'm hitting the same bug, but not sure (i will try to check next >> week). this is easy to reproduce, but you need 4 (at least 3) machines: >> >> setup 2 wireless cards, talking to each other (i use IBSS) on different >> machines. then setup routing like this: >> >> [1] - [WL1] - [WL2] - [2] >> >> now send more UDP traffic than the wireless link can handle (iperf -u -b >> 50M for example) between [1] and [2]. watch the free memory get less and >> less at [WL1] until it chrashes. > > forgot to add: [1] and [2] are connected by ethernet to [WL1/2]... > (obviously?) > > bruno > Hi, I tested the same network configuration used by bruno: PC1<--ethernet cable-->Device1<--wireless link-->Device2<--ethernet cable-->PC2 but I injected packets using a VAP in monitor mode on both wireless devices. I used UDP iperf traffic (50Mbps) from PC1 to PC2 as data stream. I agree with bruno, I think the main aspect of the test is to transmit a traffic steam that the wireless link is not able to handle. In order to trigger the crash, if the device is EDCA capable, I suggest to use the Best Effort hardware queue (skb->priority=3, AC_queue=2 in the ieee80211_select_queue()) for all data packets. Regards Lorenzo -- 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
