All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Walle <walle@corscience.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] UNDERRUN / PHY ERR in /sys/kernel/debug/ath9k/phy0/recv
Date: Fri, 21 Jan 2011 09:42:37 +0100	[thread overview]
Message-ID: <4D3946FD.4070405@corscience.de> (raw)
In-Reply-To: <AANLkTindHZROKUsJuyP5ATGX0=XOVypnrVyVeLABEPY+@mail.gmail.com>

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

  reply	other threads:[~2011-01-21  8:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 16:24 [ath9k-devel] UNDERRUN / PHY ERR in /sys/kernel/debug/ath9k/phy0/recv Bernhard Walle
2011-01-20  9:53 ` Bernhard Walle
2011-01-20 10:07   ` Mohammed Shafi
2011-01-20 10:13     ` Bernhard Walle
2011-01-20 10:18       ` Mohammed Shafi
2011-01-20 22:39 ` Luis R. Rodriguez
2011-01-21  8:42   ` Bernhard Walle [this message]
2011-01-21 18:59     ` Kyungwan Nam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D3946FD.4070405@corscience.de \
    --to=walle@corscience.de \
    --cc=ath9k-devel@lists.ath9k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.