On Wed, Sep 7, 2011 at 8:37 PM, Adrian Chadd adr...@freebsd.org wrote:
Right. The reason you won't see unable to stop RX dma is because it
hasn't locked up anything like that..
Ahh, so you think this possible could be a precursor to the DMA storm?
That looks like my solution. But I have extra
On 8 September 2011 19:42, Daniel Smith viscous.liq...@gmail.com wrote:
On Wed, Sep 7, 2011 at 8:37 PM, Adrian Chadd adr...@freebsd.org wrote:
Right. The reason you won't see unable to stop RX dma is because it
hasn't locked up anything like that..
Ahh, so you think this possible could be a
On Thu, Sep 08, 2011 at 07:42:19AM -0400, Daniel Smith wrote:
For us we can reliably recreate it when we have high gain reception
(70+ dB) combined with a high incoming frame rate. I am wondering if
(and the reason for the post) the RF front-end is being over driven.
Therefore not a bug that
Greetings,
I am running into a situation where I believe the RF front-end (AR9106)
is being over driven. The configuration being used is a high-gain
antenna with an inline LNA attached to a SparkLAN WMIA-199NI. The
interface is put into monitor mode and set the fcsfail flag. The
interface is
On 7 September 2011 22:59, Daniel Smith viscous.liq...@gmail.com wrote:
Greetings,
I am running into a situation where I believe the RF front-end (AR9106)
is being over driven. The configuration being used is a high-gain
antenna with an inline LNA attached to a SparkLAN WMIA-199NI. The
Thanks for the quick response Adrian.
On Wed, Sep 7, 2011 at 11:47 AM, Adrian Chadd adr...@freebsd.org wrote:
If the DMA RX stop storm occured then it meant the NIC thought it hit
the end of the RX descriptor list (whether you did or not) and it just
kept signalling it couldn't write packets
On 8 September 2011 02:04, Daniel Smith viscous.liq...@gmail.com wrote:
Thanks for the quick response Adrian.
No worries.
I am not certain it is in fact the DMA RX stop storm. The occurrence
often coincided when the storm use to be much more pervasive. Now we
still see it even when there is
