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: Tue, 23 Dec 2014 18:17:05 +0100 [thread overview]
Message-ID: <5499A391.2060705@rempel-privat.de> (raw)
In-Reply-To: <CA+A7n+hbr2ctPkSta9-MWT1opAT2hCB9jYHvFu7N3C_ZvxXSzw@mail.gmail.com>
Am 23.12.2014 um 16:31 schrieb Jeremy Audet:
> Hi Oleksij,
>
> Sure thing. I cloned your ath9k-htc-firmware-blob repository and
> copied the htc_9271.fw file to /usr/lib/firmware/. I then plugged in
> the TL-WN722N USB adapter, brought up the wireless device with `sudo
> ip link set dev wlp0s18f2u4 up; echo $?` (return code 0), and sat back
> and waited. I did not interact with the machine beyond keeping open an
> SSH session (via a wired interface) and watching the log file. About
> five minutes later, a similar error occurred as described in my
> previous email.
>
> I've collected some logging output with the command `journalctl -k
> --since=today`. You may find this log a bit more useful than the dmesg
> log linked to in my previous email. You can find the log here:
> http://www.ichimonji10.name/downloads/tl-wn722n-journalctl.txt
>
> -Jeremy "Ichimonji10" Audet
>
So, at some point usb layer dropped connection, and reconnected in
full-speed mode, which is slow:
=================================================================
Dec 23 10:07:49 pine kernel: usb 5-4: USB disconnect, device number 9
Dec 23 10:07:49 pine kernel: ath: phy6: Failed to wakeup in 500us
Dec 23 10:07:50 pine kernel: ath: phy6: RX failed to go idle in 10 ms
RXSM=0xb063df84
Dec 23 10:07:50 pine kernel: ath: phy6: Failed to wakeup in 500us
Dec 23 10:07:50 pine kernel: usb 5-4: ath9k_htc: USB layer deinitialized
Dec 23 10:07:50 pine kernel: usb 5-4: new high-speed USB device number
10 using ehci-pci
Dec 23 10:07:51 pine kernel: usb 1-4: new full-speed USB device number 5
using ohci-pci
Dec 23 10:07:51 pine kernel: usb 1-4: not running at top speed; connect
to a high speed hub
Dec 23 10:07:51 pine kernel: usb 1-4: ath9k_htc: Firmware htc_9271.fw
requested
Dec 23 10:07:51 pine kernel: usb 1-4: ath9k_htc: Transferred FW:
htc_9271.fw, size: 51008
==================================================================
After reconnecting to fulls-speed, ath9k-htc was unusable. I would
suggest to test other cable or other usb controller.
With other words, I have no idea about the reason for initial
disconnection. It can be bad usb connection, noise or not enough power.
--
Regards,
Oleksij
next prev parent reply other threads:[~2014-12-23 17:17 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 [this message]
2014-12-23 18:05 ` Jeremy Audet
2014-12-27 4:05 ` Jeremy Audet
2014-12-27 8:21 ` Oleksij Rempel
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=5499A391.2060705@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).