From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bernhard Walle <walle@corscience.de>
Date: Fri, 21 Jan 2011 09:42:37 +0100
Subject: [ath9k-devel] UNDERRUN / PHY ERR in
	/sys/kernel/debug/ath9k/phy0/recv
In-Reply-To: <AANLkTindHZROKUsJuyP5ATGX0=XOVypnrVyVeLABEPY+@mail.gmail.com>
References: <4D2C8450.8090302@corscience.de>
	<AANLkTindHZROKUsJuyP5ATGX0=XOVypnrVyVeLABEPY+@mail.gmail.com>
Message-ID: <4D3946FD.4070405@corscience.de>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

Hi Luis,

thanks for your reply!

Am 20.01.2011 23:39, schrieb Luis R. Rodriguez:
> On Tue, Jan 11, 2011 at 8:24 AM, Bernhard Walle <walle@corscience.de> wrote:
>>
>> can somebody explain what
>>
>>> [...]
>>>            PHY ERR :      96196
>>> [...]
>>>           UNDERRUN :      96196
>>> [...]
>>
>> in /sys/kernel/debug/ath9k/phy0/recv actually means. Is that normal, or
>> a hardware problem, or a driver problem?
> 
> Kyungwan has explained to me:
> 
> We have 3 types of underrun, fifo_underrun, tx_data_underrun_err and
> tx_dlmtr_underrun_err. All 3 underruns happen because there is not
> enough data for transmission. But when happens and how to handle are
> slightly different for each type.

And what does it mean? Is that critical? Normal?


Regards,
Bernhard