effort on investigation. Thanks!
Regards,
Kyungwan
-Original Message-
From: Bernhard Walle [mailto:wa...@corscience.de]
Sent: Friday, January 21, 2011 12:43 AM
To: Luis R. Rodriguez
Cc: ath9k-devel@lists.ath9k.org; Kyungwan Nam
Subject: Re: [ath9k-devel] UNDERRUN / PHY ERR in
/sys/kernel/debug/
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 wrote:
>>
>> can somebody explain what
>>
>>> [...]
>>>PHY ERR : 96196
>>> [...]
>>> UNDERRUN : 96196
>>> [...]
>>
>> in /sys/kernel/d
On Tue, Jan 11, 2011 at 8:24 AM, Bernhard Walle wrote:
> Hello ath9k experts,
>
> can somebody explain what
>
>> [...]
>> PHY ERR : 96196
>> [...]
>> UNDERRUN : 96196
>> [...]
>
> in /sys/kernel/debug/ath9k/phy0/recv actually means. Is that normal, or
> a hardware pr
On Thu, Jan 20, 2011 at 3:43 PM, Bernhard Walle wrote:
> Hello,
>
> Am 20.01.2011 11:07, schrieb Mohammed Shafi:
>> On Thu, Jan 20, 2011 at 3:23 PM, Bernhard Walle wrote:
>>> Am 11.01.2011 17:24, schrieb Bernhard Walle:
can somebody explain what
> [...]
> PHY ERR
Hello,
Am 20.01.2011 11:07, schrieb Mohammed Shafi:
> On Thu, Jan 20, 2011 at 3:23 PM, Bernhard Walle wrote:
>> Am 11.01.2011 17:24, schrieb Bernhard Walle:
>>>
>>> can somebody explain what
>>>
[...]
PHY ERR : 96196
[...]
UNDERRUN : 96196
[
On Thu, Jan 20, 2011 at 3:23 PM, Bernhard Walle wrote:
> Hi again,
>
> Am 11.01.2011 17:24, schrieb Bernhard Walle:
>>
>> can somebody explain what
>>
>>> [...]
>>> PHY ERR : 96196
>>> [...]
>>> UNDERRUN : 96196
>>> [...]
>>
>> in /sys/kernel/debug/ath9k/phy0/recv ac
Hi again,
Am 11.01.2011 17:24, schrieb Bernhard Walle:
>
> 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 p
Hello ath9k experts,
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?
Thanks for any pointers!
Regards,
Bernhar