From: Oleksij Rempel <linux@rempel-privat.de>
To: Jeremy Audet <ichimonji10@gmail.com>
Cc: linux-wireless@vger.kernel.org, Adrian Chadd <adrian@freebsd.org>
Subject: Re: bug report for ath9k_htc driver
Date: Sat, 27 Dec 2014 09:21:46 +0100 [thread overview]
Message-ID: <549E6C1A.7010805@rempel-privat.de> (raw)
In-Reply-To: <CA+A7n+iHKBxy3qfjzrnN7GdZhJ-WwoDdi6hjw8RSaDs8TBznvw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3974 bytes --]
I found this note with similar kernel log like yours:
http://www.linuxforums.org/forum/hardware-peripherals/195227-tl-wn722n-backtrack-5-a.html
Can you please test this workaround?
Am 27.12.2014 um 05:05 schrieb Jeremy Audet:
> Sending this again b/c of a delivery error. [9] Sorry for the possible spam.
>
> Hi again,
>
> When last I wrote, I stated that the issue lay with the USB cradle I'd been
> using, and I'd discarded it in favor of plugging the TL-WN722N directly in to
> my PC. I also mentioned that I'd gotten a wireless access point up and running
> for 30 minutes. Not five minutes after I sent that email, the same error I've
> described earlier occurred, and the USB wireless adapter was demoted to
> full-speed mode.
>
> This is bothersome, so in an effort to rule out sources of error, I ran a series
> of simple tests, all having this structure:
>
> 1. Start logging out kernel messages with the `journalctl -k --follow -n 0`
> command.
> 2. Plug a TP-LINK TL-WN722N wireless adapter directly in to a USB port.
> 3. Turn on the adapter with the `ip link set dev $device up` command.
> 4. Wait for an error.
> 5. Stop collecting logging output. (Send CTRL-C to `journalctl`.)
> 6. Unplug TL-WN722N.
>
> Here's the purpose of the above:
>
> * It is possible that a specific USB port or ports on my motherboard are flaky.
> To help rule this out, run the test with three different USB ports on my
> motherboard. Two of the ports are built directly in to the back panel of the
> motherboard, and the third connects to header pins on the motherboard.
> * It is possible that the specific TL-WN722N I am using is flaky. To help rule
> this out, run the test with a second TL-WN722N. [1, 2]
>
> Notably, I am also using the `htc_9271.fw` firmware file available at
> https://github.com/olerem/ath9k-htc-firmware-blob for this test. As a refresher,
> here's some other info about my system:
>
> $ uname -a
> Linux pine 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC
> 2014 x86_64 GNU/Linux
> $ ip -V
> ip utility, iproute2-ss141009
>
> And here's some output from `lsusb -v` for the old and new TL-WN722N devices:
>
> * old: http://www.ichimonji10.name/downloads/tl-wn722n-old-lsusb.txt
> * new: http://www.ichimonji10.name/downloads/tl-wn722n-lsusb.txt
>
> Here's the test results. Port 1, 2, and 3 are the upper back panel, lower back
> panel and header pins on the motherboard, respectively.
>
> * Port 1, old adapter: fail [3]
> * Port 1, new adapter: fail [4]
> * Port 2, old adapter: fail [5]
> * Port 2, new adapter: fail [6]
> * Port 3, old adapter: fail [7]
> * Port 3, new adapter: fail [8]
>
> [1] I bought a TL-WN722N several years ago, eventually stuck it in the bottom of
> my tool kit and forgot about it until just now. I bought the two TL-WN722Ns
> several years apart, so it is unlikely that the two adapters both suffer
> from e.g. a manufacturing defect. They were bought on 2014-11-10 and
> 2012-09-25.
> [2] lsusb -v: http://www.ichimonji10.name/downloads/tl-wn722n-old-lsusb.txt
> [3] http://www.ichimonji10.name/downloads/2014-12-26-p1-old.txt
> [4] http://www.ichimonji10.name/downloads/2014-12-26-p1-new.txt
> [5] http://www.ichimonji10.name/downloads/2014-12-26-p2-old.txt
> [6] http://www.ichimonji10.name/downloads/2014-12-26-p2-new.txt
> [7] http://www.ichimonji10.name/downloads/2014-12-26-p3-old.txt
> [8] http://www.ichimonji10.name/downloads/2014-12-26-p3-new.txt
> [9] Technical details of permanent failure:
> Google tried to deliver your message, but it was rejected by the
> server for the recipient domain vger.kernel.org by vger.kernel.org.
> [...] The error that the other server returned was: 550 5.7.1
> Content-Policy reject msg: The message contains HTML subpart,
> therefore we consider it SPAM or Outlook Virus. TEXT/PLAIN is
> accepted.
>
--
Regards,
Oleksij
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
next prev parent reply other threads:[~2014-12-27 8:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 23:53 bug report for ath9k_htc driver Jeremy Audet
2014-12-23 7:35 ` Oleksij Rempel
2014-12-23 15:31 ` Jeremy Audet
2014-12-23 17:17 ` Oleksij Rempel
2014-12-23 18:05 ` Jeremy Audet
2014-12-27 4:05 ` Jeremy Audet
2014-12-27 8:21 ` Oleksij Rempel [this message]
2015-01-03 5:54 ` Jeremy Audet
2015-01-13 22:46 ` Jeremy Audet
2015-01-14 16:23 ` Oleksij Rempel
2015-01-19 0:35 ` Jeremy Audet
2015-01-19 1:31 ` Jeremy Audet
2015-01-19 6:53 ` Oleksij Rempel
2015-01-19 7:03 ` 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=549E6C1A.7010805@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=adrian@freebsd.org \
--cc=ichimonji10@gmail.com \
--cc=linux-wireless@vger.kernel.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).