lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 30 Jul 2011 13:07:31 -0500
From:	Larry Finger <Larry.Finger@...inger.net>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
CC:	Andreas Hartmann <andihartmann@...19freenet.de>,
	Stanislaw Gruszka <sgruszka@...hat.com>,
	Ivo van Doorn <IvDoorn@...il.com>,
	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
	Alan Piszcz <ap@...arrain.com>,
	"users@...x00.serialmonkey.com" <users@...x00.serialmonkey.com>
Subject: Re: [PATCH] rt2x00: rt2800: fix zeroing skb structure

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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ