Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 09 Feb 2013 10:47:46 +0200
From:      Ian FREISLICH <ianf@clue.co.za>
To:        Hans Petter Selasky <hselasky@c2i.net>
Cc:        freebsd-current@freebsd.org
Subject:   Re: uath panic on insert.
Message-ID:  <E1U4667-0003Jw-1f@clue.co.za>
In-Reply-To: <201302082353.13581.hselasky@c2i.net>
References:  <201302082353.13581.hselasky@c2i.net> <201302082218.24033.hselasky@c2i.net> <E1U3sZh-0000aA-Kx@clue.co.za> <E1U3vj4-0001px-1D@clue.co.za>

next in thread | previous in thread | raw e-mail | index | archive | help
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?

Ian

-- 
Ian Freislich



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1U4667-0003Jw-1f>