All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] WARNING with ath9k_htc on TL-WN721N
Date: Thu, 05 Sep 2013 16:32:13 +0200	[thread overview]
Message-ID: <522895ED.2080403@rempel-privat.de> (raw)
In-Reply-To: <20130905142122.GE1570@ritirata.org>

Am 05.09.2013 16:21, schrieb Antonio Quartulli:
> On Thu, Sep 05, 2013 at 04:09:04PM +0200, Oleksij Rempel wrote:
>> Forgot attachment.
>>
>>
>> Am 05.09.2013 16:07, schrieb Oleksij Rempel:
>>> Hi,
>>>
>>> thank you.
>>>
>>> please do some tests for me.
>>>
>>> 1. run wireless adapter without other devices on this bus.
>>>
>
> Ok Oleksij, I'll try to do these tests soonish. You think the problem is
> triggered by a scan operation?
>
> If so, I'll try to reproduce it by scanning. Till now I had no clue about the
> cause.

Probably no only scan. Normally if you use network manager, it will scan 
each 160 seconds or so. In this case you will get this warning lot more 
often. Probably it comes together: hight network traffic + channel scan 
+ usb traffic of other devices on same bus.


-- 
Regards,
Oleksij

WARNING: multiple messages have this Message-ID (diff)
From: Oleksij Rempel <linux@rempel-privat.de>
To: Antonio Quartulli <ordex@autistici.org>
Cc: ath9k-devel <ath9k-devel@lists.ath9k.org>,
	linux-wireless@vger.kernel.org
Subject: Re: WARNING with ath9k_htc on TL-WN721N
Date: Thu, 05 Sep 2013 16:32:13 +0200	[thread overview]
Message-ID: <522895ED.2080403@rempel-privat.de> (raw)
In-Reply-To: <20130905142122.GE1570@ritirata.org>

Am 05.09.2013 16:21, schrieb Antonio Quartulli:
> On Thu, Sep 05, 2013 at 04:09:04PM +0200, Oleksij Rempel wrote:
>> Forgot attachment.
>>
>>
>> Am 05.09.2013 16:07, schrieb Oleksij Rempel:
>>> Hi,
>>>
>>> thank you.
>>>
>>> please do some tests for me.
>>>
>>> 1. run wireless adapter without other devices on this bus.
>>>
>
> Ok Oleksij, I'll try to do these tests soonish. You think the problem is
> triggered by a scan operation?
>
> If so, I'll try to reproduce it by scanning. Till now I had no clue about the
> cause.

Probably no only scan. Normally if you use network manager, it will scan 
each 160 seconds or so. In this case you will get this warning lot more 
often. Probably it comes together: hight network traffic + channel scan 
+ usb traffic of other devices on same bus.


-- 
Regards,
Oleksij

  reply	other threads:[~2013-09-05 14:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 10:09 [ath9k-devel] WARNING with ath9k_htc on TL-WN721N Antonio Quartulli
2013-09-05 10:09 ` Antonio Quartulli
2013-09-05 10:25 ` [ath9k-devel] " Oleksij Rempel
2013-09-05 10:25   ` Oleksij Rempel
2013-09-05 10:32   ` [ath9k-devel] " Antonio Quartulli
2013-09-05 10:32     ` Antonio Quartulli
2013-09-05 14:07     ` [ath9k-devel] " Oleksij Rempel
2013-09-05 14:07       ` Oleksij Rempel
2013-09-05 14:09       ` [ath9k-devel] " Oleksij Rempel
2013-09-05 14:09         ` Oleksij Rempel
2013-09-05 14:21         ` [ath9k-devel] " Antonio Quartulli
2013-09-05 14:21           ` Antonio Quartulli
2013-09-05 14:32           ` Oleksij Rempel [this message]
2013-09-05 14:32             ` Oleksij Rempel

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=522895ED.2080403@rempel-privat.de \
    --to=linux@rempel-privat.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.