From owner-freebsd-usb@FreeBSD.ORG Wed Feb 25 07:08:24 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58FAE106564A; Wed, 25 Feb 2009 07:08:24 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.swip.net [212.247.154.97]) by mx1.freebsd.org (Postfix) with ESMTP id 5EC858FC0C; Wed, 25 Feb 2009 07:08:23 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=hbAlcvKlQP8A:10 a=2MW6OuLsUmcA:10 a=MXw7gxVQKqGXY79tIT8aFQ==:17 a=l-qSWZbQbNMgXLtZucEA:9 a=PJ8cYhnkZNaszfwbifkA:7 a=00odyTNQNy-D10Fxkp0GhLthHSwA:4 a=50e4U0PicR4A:10 a=2S6gNbZwQW9wkUAZ:21 a=h1DbZxB0Et45STE9:21 Received: from [62.113.132.61] (account mc467741@c2i.net HELO laptop) by mailfe04.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1200831684; Wed, 25 Feb 2009 08:08:21 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org, Andrew Thompson , Sam Leffler Date: Wed, 25 Feb 2009 08:10:50 +0100 User-Agent: KMail/1.9.7 References: <200902250112.n1P1CQGK027474@www.freebsd.org> In-Reply-To: <200902250112.n1P1CQGK027474@www.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902250810.51822.hselasky@c2i.net> Cc: freebsd-gnats-submit@freebsd.org, Alexander Melkov Subject: Re: usb/132080: [patch] [usb] Kernel panic after NOMEM caused by rum card X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2009 07:08:24 -0000 Hi, The RUM timeouts you are seeing I am aware about. They happen most likely because the WLAN channel is set when the device is in the running state on the RUM device due to WLAN re-keying or something like that. Maybe you can confirm that the time from start of device with heavy download until it gets the first timeout is 10minutes? This issue is actually a RUM firmware issue. If it has frames pending for TX and we set the channel, the chip will simply reset or do strange things. Possible RUM workaround: Set the same WLAN channel only once. I think Andrew Thompson is working on this. I have some patches in the USB P4 project for 8-current which fix the problem to a level where TX will dissappear for 4 seconds every 10 minutes, but there will be no device timeout! The final patch should solve the problem completely, but I need some help to figure out when we should ignore set_channel requests. --HPS On Wednesday 25 February 2009, Alexander Melkov wrote: > >Number: 132080 > >Category: usb > >Synopsis: [patch] [usb] Kernel panic after NOMEM caused by rum card > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Wed Feb 25 01:20:02 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Alexander Melkov > >Release: 7.1-STABLE > >Organization: > >Environment: > > FreeBSD melkov.ru 7.1-STABLE FreeBSD 7.1-STABLE #14: Tue Feb 24 06:28:45 > MSK 2009 root_at_melkov.ru:/usr/obj/usr/src/sys/MELKOV amd64 > > >Description: > > I have device which is Cisco-Linksys Compact Wireless-G USB Adapter > that runs in hostap mode (i.e. wifi access point). Sometimes it > malfunctions (that may happen several times a day), at that moment I have > message "rum0: could not transmit buffer: NOMEM" from kernel. Right after > the message kernel crashes upon read from (nearly) null address. >