On Thu, Jan 8, 2009 at 1:41 PM, Bob Copeland <bcopeland@xxxxxxxxx> wrote: > On Thu, Jan 8, 2009 at 12:55 PM, Hugh Dickins <hugh@xxxxxxxxxxx> wrote: >> Let me see if I can reproduce the ath5k BUG with a straightforward >> memhog, repeatedly dirtying more anon memory than RAM can provide. >> Is there something suitable I could run to exercise that wireless >> path concurrently? It was just idling when I hit the BUGs before. > > Receiving any packets will do it, in your case it was probably > beacons from nearby APs if you weren't using the wifi. So iperf > or similar will work. Actually it's probably enough to just intentionally fail one of the allocations in the driver. I'll do that and let you know if I can easily break it. -- Bob Copeland %% www.bobcopeland.com -- 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
