On 07/30/2011 12:07 PM, Justin Piszcz wrote:
On Sat, 30 Jul 2011, Andreas Hartmann wrote:
Hi Justin,
if you want to test, if the module works stable, run this script for one
or two hours. It will stress the driver and the hardware.
If it doesn't crash and if the throughput is stable, you can hope, that
the driver is ok for daily work.
#!/bin/sh
dest="server" # set the servername
while true ; do
netperf -t TCP_MAERTS -H $dest
netperf -t TCP_STREAM -H $dest
netperf -t TCP_SENDFILE -H $dest
done
Start the script on the client. On the server start netserver.
You get netperf from http://www.netperf.org/netperf/
Andreas
Hello Andreas,
Thanks for the suggestion; however, it is crashing repeatedly after about 5-10
minutes, so it is not needed yet.
Here you go, crash 2:
http://home.comcast.net/~jpiszcz/20110730/2630-rt2800usb-crash2p1.jpg
http://home.comcast.net/~jpiszcz/20110730/2630-rt2800usb-crash2p2.jpg
This is likely progress as the crash is in a different place.
The page fault this time is at rt2800usb_get_txwi+0xc. That translates back to
line 382 of file rt2800usb.c, which says
if (entry->queue->qid == QID_BEACON)
I have no idea why entry->queue->qid is wrong here, but likely one of the
smarter people who knows a lot more about the device will be able to figure it out.
Larry
--
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
