Date: Wed, 29 Oct 2014 08:50:23 -0700 From: Rui Paulo <rpaulo@me.com> To: sbruno@freebsd.org Cc: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: urtwn(4) Random freezes, urtwn_getbuf: out of xmit buffers Message-ID: <87B376C9-72D1-41D8-868C-45908D642CA1@me.com> In-Reply-To: <1414525275.43009.3.camel@bruno> References: <1414525275.43009.3.camel@bruno>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 28, 2014, at 12:41, Sean Bruno <sbruno@ignoranthack.me> wrote: >=20 > 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. >=20 > hw.usb.urtwn.debug: 1 >=20 > 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 That means the firmware is stuck and is holding transmit buffers, so we = have no more in the unused list. > Additionally, I get the following at module load time: >=20 > 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 I'm not sure what this is. -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87B376C9-72D1-41D8-868C-45908D642CA1>