From owner-freebsd-current@FreeBSD.ORG  Sat Feb  9 09:16:54 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 7C340F0C
 for <freebsd-current@freebsd.org>; Sat,  9 Feb 2013 09:16:54 +0000 (UTC)
 (envelope-from hselasky@c2i.net)
Received: from swip.net (mailfe03.c2i.net [212.247.154.66])
 by mx1.freebsd.org (Postfix) with ESMTP id F0B07F51
 for <freebsd-current@freebsd.org>; Sat,  9 Feb 2013 09:16:53 +0000 (UTC)
X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED,
	BAYES_50
Received: from [176.74.213.204] (account mc467741@c2i.net HELO
 laptop015.hselasky.homeunix.org)
 by mailfe03.swip.net (CommuniGate Pro SMTP 5.4.4)
 with ESMTPA id 209076364; Sat, 09 Feb 2013 10:16:46 +0100
From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-current@freebsd.org
Subject: Re: uath panic on insert.
Date: Sat, 9 Feb 2013 10:17:56 +0100
User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; )
References: <201302082353.13581.hselasky@c2i.net>
 <E1U3vj4-0001px-1D@clue.co.za> <E1U4667-0003Jw-1f@clue.co.za>
In-Reply-To: <E1U4667-0003Jw-1f@clue.co.za>
X-Face: ?p&W)c<w+fb'sd#*]i!s!UQ[!|W8%I(I+\}LQ-Z1nB*t(u_>(+80hU; '{.$5K+zq{oC6y|
 /D'an*6mw>j'f:eBsex\Gi, <a&s"J*gPjz0nO,
 Sucb&N84|zkA2YlM?`/Vp=@Bh}pyW=TQ WtqwY'_Sy0aa~(jJCeFpDW
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201302091017.56055.hselasky@c2i.net>
Cc: Ian FREISLICH <ianf@clue.co.za>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 09:16:54 -0000

On Saturday 09 February 2013 09:47:46 Ian FREISLICH wrote:
> Hans Petter Selasky wrote:
> > On Friday 08 February 2013 22:43:17 Ian FREISLICH wrote:
> > > Hans Petter Selasky wrote:
> > > > Hi,
> > > > 
> > > > Your problem should be fixed by:
> > > > http://svnweb.freebsd.org/changeset/base/246565
> > > > 
> > > > Please test and report back if it doesn't.
> > > 
> > > It doesn't panic anymore.  Thanks.  There's a new problem though:
> > > 
> > > uath0: <Atheros Communications Inc USB WLAN Device, rev 2.00/0.01, addr
> > > 5> on usbus1 wlan1: Ethernet address: 00:11:95:d3:4a:af
> > 
> > Hi,
> > 
> > Can you try this patch:
> > http://svnweb.freebsd.org/changeset/base/246570
> 
> ugen1.5: <Atheros Communications Inc> at usbus1
> <Atheros Communications Inc USB WLAN Device, rev 2.00/0.01, addr 5> on
> usbus1 Ethernet address: 00:11:95:d3:4a:af
> uath_cmdsend: empty inactive queue
> could not init Tx queues, error 55
> uath_cmdsend: empty inactive queue
> could not set channel, error 55
> uath_cmdsend: empty inactive queue
> could not set channel, error 55
> uath_cmdsend: empty inactive queue
> could not set channel, error 55
> uath_cmdsend: empty inactive queue
> could not set channel, error 55
> uath_cmdsend: empty inactive queue
> could not set channel, error 55
> at uhub2, port 2, addr 5 (disconnected) <---
> uath_cmdsend: empty inactive queue
> uath_cmdsend: empty inactive queue
> ugen1.5: <Atheros Communications Inc> at usbus1 (disconnected)
> 
> The card still disconnects after attempting to scan unsupported
> frequencies.  The sequence above happens when I 'ifconfig wlan1
> up'.  Also, the uath driver reports 2.4GHz and 5GHz as supported
> channels for this chip but it's a D-Link DWL-G132 which is a 2.4GHz
> device.  Is this a problem for Adrian to look at?

Hi,

I see the same over here. I think it is not a USB problem.

--HPS