Return-path: Received: from mail-iw0-f174.google.com ([209.85.214.174]:65523 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757390Ab0I0XDS (ORCPT ); Mon, 27 Sep 2010 19:03:18 -0400 Received: by iwn5 with SMTP id 5so5174672iwn.19 for ; Mon, 27 Sep 2010 16:03:14 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <58E3CFACA7054DC48245C67E9D4AE07B@ChuckPC> From: "Luis R. Rodriguez" Date: Mon, 27 Sep 2010 16:02:54 -0700 Message-ID: Subject: Re: memory leak in scan with 9170? To: Chuck Crisler Cc: linux-wireless@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, Sep 27, 2010 at 4:01 PM, Luis R. Rodriguez wrote: > On Mon, Sep 27, 2010 at 3:40 PM, Chuck Crisler wrote: >> Well, (as usual) I was wrong. It isn't a memory problem. It seems that after >> some indeterminant time, the USB interface locks up. When we try to take it >> down (ifconfig wlan0 down) we get a message about outstanding urbs. By >> powering down the 9170 we can re-set the device and get it to re-associate >> and resume work. So, the problem is a USB problem. The question is if it is >> a module problem or a system problem. We are typically seeing this after >> 50-200 reassociations. If we don't reassociate, it doesn't seem to occur. >> Does anyone else have experience or insight into this? > > Upgrade. Let me clarify, 2.6.31 is not supported, its not listed on kernel.org any more as a supported kernel. You are losing valuable fixes by not moving away from it. If you don't have a plan to move, you need it, if you have policies to lock you down to old kernels, try to change it. Luis