From owner-freebsd-current@FreeBSD.ORG Tue May 19 07:08:28 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C93E1065670 for ; Tue, 19 May 2009 07:08:28 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe15.swip.net [212.247.155.193]) by mx1.freebsd.org (Postfix) with ESMTP id A79098FC15 for ; Tue, 19 May 2009 07:08:27 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=x01RqrcTYZgA:10 a=bYLFNfMPybAA:10 a=j+k/Ze5hWUCaCztCgEjzDQ==:17 a=8kQB0OdkAAAA:8 a=6I5d2MoRAAAA:8 a=Ds2_JaYoDQwa8IFOgrgA:9 a=js8qjCAYeXs5wEw1lYR-R-wmlGAA:4 a=9aOQ2cSd83gA:10 Received: from [81.191.55.181] (account mc467741@c2i.net HELO laptop) by mailfe15.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 497318872; Tue, 19 May 2009 09:08:26 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org, Weongyo Jeong Date: Tue, 19 May 2009 09:11:01 +0200 User-Agent: KMail/1.9.7 References: <90a5caac0905171354k6e7c008eye18bd69aa543eaa6@mail.gmail.com> <90a5caac0905181508m7024377as8d70c89694a21e26@mail.gmail.com> <20090519044941.GC42412@weongyo.cdnetworks.kr> In-Reply-To: <20090519044941.GC42412@weongyo.cdnetworks.kr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905190911.01576.hselasky@c2i.net> Cc: Lucius Windschuh Subject: Re: Panics and potential memory corruption when pulling out a uath device X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 07:08:28 -0000 On Tuesday 19 May 2009, Weongyo Jeong wrote: > On Tue, May 19, 2009 at 12:08:45AM +0200, Lucius Windschuh wrote: > > 2009/5/18 Hans Petter Selasky : > > > Regarding the first panic, there seems to be a detach race in both upgt > > > and uath, which is not USB related. Try this patch: > > > > > > http://perforce.freebsd.org/chv.cgi?CH=162250 > > > > This fixes not only the first panic. > > I can't provoke any panic by pulling out the active device. Thanks. > > Could you please test with this patch that is slightly different with > Hans's patch? It try to unsetup after stopping the device. > > If no problems I'd commit it. > > regards, > Weongyo Jeong Hi, I had added the wrong ID to the driver. Now it seems to almost work. What does the following error code mean? When I run wpa_cli I see some valid scan results. I have not tried to associate yet. uath0: could not set channel, error 55 uath0: uath_cmdsend: empty inactive queue uath0: could not set channel, error 55 uath0: uath_cmdsend: empty inactive queue uath0: could not set channel, error 55 uath0: uath_cmdsend: empty inactive queue uath0: could not set channel, error 55 uath0: uath_cmdsend: empty inactive queue uath0: could not set channel, error 55 uath0: uath_cmdsend: empty inactive queue uath0: could not set channel, error 55 uath0: uath_cmdsend: empty inactive queue uath0: could not set channel, error 55 uath0: uath_cmdsend: empty inactive queue uath0: could not set channel, error 55 --HPS