Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Feb 2012 13:46:57 -0800
From:      Adrian Chadd <adrian@freebsd.org>
To:        Lev Serebryakov <lev@serebryakov.spb.ru>
Cc:        freebsd-wireless@freebsd.org
Subject:   Re: "ath0: device timeout" when environment is clear
Message-ID:  <CAJ-Vmo=OuBC65ie7t2LeQof4mPngrEyNPwwuJuijk0W%2BVjGCDg@mail.gmail.com>
In-Reply-To: <208667374.20120203002726@serebryakov.spb.ru>
References:  <743722267.20120202195757@serebryakov.spb.ru> <CAJ-Vmo=js__O2YfPuRQTH0WfaDg1oo0LmugoCV5hi6HUtksprQ@mail.gmail.com> <1292923023.20120202232810@serebryakov.spb.ru> <CAJ-VmonApDTGUU0JgFWQApktHW0Xi6Fq2dbDNkP_Hu_Q29KL9g@mail.gmail.com> <208667374.20120203002726@serebryakov.spb.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

The lack of TX buffers in that list (they're all RX buffers) means that the
TX queue is empty.

So, the "device timeout" is incorrect - the device didn't timeout, we just
didn't queue any frames to the device but somehow the TX watchdog was set.
Or, the watchdog wasn't cleared upon TX queue processing.

I wonder why this is occuring. ;-)


Adrian



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=OuBC65ie7t2LeQof4mPngrEyNPwwuJuijk0W%2BVjGCDg>