linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:07:47 +0200	[thread overview]
Message-ID: <52289033.8080205@rempel-privat.de> (raw)
In-Reply-To: <20130905103204.GB1570@ritirata.org>

Hi,

thank you.

please do some tests for me.

1. run wireless adapter without other devices on this bus.

> Bus 002 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
> Bus 002 Device 011: ID 03f0:8607 Hewlett-Packard Optical Mobile Mouse
> Bus 002 Device 005: ID 0403:6001 Future Technology Devices International, Ltd
> FT232 USB-Serial (UART) IC
> Bus 002 Device 006: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module

probably Bluetooth can't be removed, so disable it by software.

2. if this warning disappear, plug them back and rung kernel with 
attached patch. I wont to see if this warning related to channel scan.

3. try latest wireless-next kernel
https://git.kernel.org/cgit/linux/kernel/git/linville/wireless-next.git/

there are some patches which will affect usb communication, this will be 
visible on your hardware, in good or bad way. Will see how it performs 
in your situation.

I assume this warning is related to usb bandwidth. Since we use BULK 
transfer, we will get only rest of it. If other devices use ISO or 
Interrupt, They well have priority.

> I'm not using the Intel card listed in lspci. (the iwldvm module is loaded but
> the interface is down).
>
> Cheers,
>
>
> On Thu, Sep 05, 2013 at 12:25:06PM +0200, Oleksij Rempel wrote:
>> Am 05.09.2013 12:09, schrieb Antonio Quartulli:
>>> Hello list,
>>>
>>> I ma connected to my WPA2-PSK protected network and from time to time I get the
>>> following warning in dmesg. I don't experience any malfunctionng but I thought
>>> it was worth reporting. My kernel version is linux-3.10.10. I remember I've seen
>>> this warning also with previous versions.
>>>
>>> The device I use is a TP-LINK TL-WN721N.
>>> lsusb says:
>>>
>>> Bus 002 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
>>>
>>> Cheers,
>>>
>>
>> Hi Antonio,
>>
>> pleas send out of lsusb and lspci.
>>
>>
>> --
>> Regards,
>> Oleksij
>


-- 
Regards,
Oleksij

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 10:09 WARNING with ath9k_htc on TL-WN721N Antonio Quartulli
2013-09-05 10:25 ` Oleksij Rempel
2013-09-05 10:32   ` Antonio Quartulli
2013-09-05 14:07     ` Oleksij Rempel [this message]
2013-09-05 14:09       ` Oleksij Rempel
2013-09-05 14:21         ` Antonio Quartulli
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=52289033.8080205@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ordex@autistici.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).