From owner-freebsd-current@FreeBSD.ORG Thu May 21 03:48:17 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 AB008106566B for ; Thu, 21 May 2009 03:48:17 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228]) by mx1.freebsd.org (Postfix) with ESMTP id 710448FC13 for ; Thu, 21 May 2009 03:48:17 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: by rv-out-0506.google.com with SMTP id k40so321037rvb.43 for ; Wed, 20 May 2009 20:48:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent:organization:x-operation-sytem; bh=TzA1ShbTzvmegPbxH/lFMqkPhOWGl9ekdqAbztJlpzQ=; b=O6iQnDR+Z1uPYLKAFnS+r7EG8Kz34wNSUMrJp9x4/8f1EGdRSUJUnMHTEy+Tep7iAX PhfCXVbKHAgBbjBHzxP+ionkr1dICz+IbWHhQtjBojbX5FIdOx/dpqItaX/+1sklwDDb AYauk0jc4sMXw7+cFfPVShISuzNGkUuWYDjHQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent:organization:x-operation-sytem; b=RLoQPl+ZUpVf/gAiqRgAUgGBFYgk5VA9cN3ybjHhwsNx/8C7Wo4LbtiQx5AdgMqvZy 34KziqDueRtTRKQ69VqbAE68eeh/LpF5CfIwopVSye4ceoS04lz3BNIURpkMf726ywBg coE7tsqLr+5RjpTbBZuG52yzOlAYygdyLsbB0= Received: by 10.141.20.6 with SMTP id x6mr929891rvi.40.1242877697025; Wed, 20 May 2009 20:48:17 -0700 (PDT) Received: from weongyo ([114.111.62.249]) by mx.google.com with ESMTPS id c20sm5626880rvf.0.2009.05.20.20.48.14 (version=SSLv3 cipher=RC4-MD5); Wed, 20 May 2009 20:48:15 -0700 (PDT) Received: by weongyo (sSMTP sendmail emulation); Thu, 21 May 2009 12:48:11 +0900 From: Weongyo Jeong Date: Thu, 21 May 2009 12:48:11 +0900 To: Hans Petter Selasky Message-ID: <20090521034811.GA88745@weongyo.cdnetworks.kr> Mail-Followup-To: Hans Petter Selasky , freebsd-current@freebsd.org, Lucius Windschuh References: <90a5caac0905171354k6e7c008eye18bd69aa543eaa6@mail.gmail.com> <90a5caac0905181508m7024377as8d70c89694a21e26@mail.gmail.com> <20090519044941.GC42412@weongyo.cdnetworks.kr> <200905190911.01576.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200905190911.01576.hselasky@c2i.net> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD Cc: Lucius Windschuh , freebsd-current@freebsd.org 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 Reply-To: Weongyo Jeong List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2009 03:48:17 -0000 On Tue, May 19, 2009 at 09:11:01AM +0200, Hans Petter Selasky wrote: > 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 It means that by some reasons the device didn't answer to the command request the driver queued on the command queue, so all of commands are waiting the device's responses. regards, Weongyo Jeong