All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <ordex@autistici.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] WARNING with ath9k_htc on TL-WN721N
Date: Thu, 5 Sep 2013 16:21:22 +0200	[thread overview]
Message-ID: <20130905142122.GE1570@ritirata.org> (raw)
In-Reply-To: <52289080.80604@rempel-privat.de>

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.
> >
> >> 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.

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.

Cheers,


-- 
Antonio Quartulli

..each of us alone is worth nothing..
Ernesto "Che" Guevara
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130905/75bc3753/attachment.pgp 

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

[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]

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.
> >
> >> 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.

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.

Cheers,


-- 
Antonio Quartulli

..each of us alone is worth nothing..
Ernesto "Che" Guevara

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-09-05 14:21 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         ` Antonio Quartulli [this message]
2013-09-05 14:21           ` Antonio Quartulli
2013-09-05 14:32           ` [ath9k-devel] " Oleksij Rempel
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=20130905142122.GE1570@ritirata.org \
    --to=ordex@autistici.org \
    --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.