Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Oct 2014 12:11:47 -0700
From:      Sean Bruno <sbruno@ignoranthack.me>
To:        Kevin Lo <kevlo@FreeBSD.org>
Cc:        FreeBSD Net <freebsd-net@freebsd.org>
Subject:   Re: urtwn(4) Random freezes, urtwn_getbuf: out of xmit buffers
Message-ID:  <1414696307.1773.12.camel@bruno>
In-Reply-To: <1414692589.1773.11.camel@bruno>
References:  <1414525275.43009.3.camel@bruno> <20141030025241.GA73148@ns.kevlo.org>  <1414692589.1773.11.camel@bruno>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2014-10-30 at 11:09 -0700, Sean Bruno wrote:
> On Thu, 2014-10-30 at 10:52 +0800, Kevin Lo wrote:
> > On Tue, Oct 28, 2014 at 12:41:15PM -0700, Sean Bruno wrote:
> > > 
> > > It looks like recent HEAD seems to fail intermittently here on my home
> > > network.  It will recover, but urtwn(4) seems to lose an ack or
> > > something on txmit.  turning on debug, yields this message during the
> > > hang event.
> > > 
> > > hw.usb.urtwn.debug: 1
> > > 
> > > Oct 28 12:34:58 bruno kernel: _urtwn_getbuf: _urtwn_getbuf: out of xmit
> > > buffers
> > > Oct 28 12:34:58 bruno kernel: urtwn_getbuf: urtwn_getbuf: stop queue
> > > Oct 28 12:34:58 bruno kernel: _urtwn_getbuf: _urtwn_getbuf: out of xmit
> > > buffers
> > > Oct 28 12:34:58 bruno kernel: urtwn_getbuf: urtwn_getbuf: stop queue
> > > 
> > > Additionally, I get the following at module load time:
> > > 
> > > urtwn0: <vendor 0x0bda product 0x8176, class 0/0, rev 2.00/2.00, addr 1>
> > > on usbus0
> > > urtwn0: could not read efuse byte at address 0x10
> > > urtwn0: could not read efuse byte at address 0x18
> > 
> > Strange.  What the wlan dongle model do you use?  I have the RTL8188CUS 
> > wireless usb adaptor (Edimax EW-7811Un), but I cannot reproduce that issue.
> > 
> > 	Kevin
> 
> 
> urtwn0: <vendor 0x0bda product 0x8176, class 0/0, rev 2.00/2.00, addr 3>
> on usbus0
> urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R
> 
> This is one that I "aquired" from hiren@ ... I assume its supposed to
> work fine.
> 
> sean
> 

I connected this device to a seperate computer and was seeing the same
type of timeouts.  Just wanted to make sure that it wasn't a USB
controller issues.

sean




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1414696307.1773.12.camel>