From: Christian Lamparter <chunkeey@googlemail.com>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: linux-wireless@vger.kernel.org,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
Seth Forshee <seth.forshee@canonical.com>
Subject: Re: FUSB200 xhci issue
Date: Mon, 22 Jul 2013 23:23:10 +0200 [thread overview]
Message-ID: <3155156.7uKpoiQrxp@blech> (raw)
In-Reply-To: <51ED9A6D.4070900@rempel-privat.de>
On Monday, July 22, 2013 10:47:41 PM Oleksij Rempel wrote:
> Am 22.07.2013 21:54, schrieb Christian Lamparter:
> > Hello!
> >
> > On Monday, July 22, 2013 05:21:54 PM Oleksij Rempel wrote:
> >> i'm one of ath9k_htc devs. Currently i'm working on usb_suspend issue of
> >> this adapters. Looks like ar9271 and ar7010 have FUSB200, and i
> >> accidentally discovered that 9170 have it too. Are there any issue with
> >> usb-suspend + xhci controllers by you? Did you some how specially
> >> handled it?
> >
> > No, I haven't heard any complains about xhci + suspend. In fact,
> > it's working fine with the NEC xhci I have. I also have a AR9271
> > and AR7010, so if you want I could try if they survive a suspend
> > +resume cycle when attached.
> >
> > But, I do have a bug-report from someone else who has/had? problems
> > with carl9170 and xhci. If you want, you can get the details from:
> > "carl9170 A-MPDU transmit problem":
> > <http://comments.gmane.org/gmane.linux.kernel.wireless.general/104597>
> >
> > The likely cause is related to Intel's xhci silicon (Ivy Bridge is
> > affected, but I don't know about Haswell):
> > <http://permalink.gmane.org/gmane.linux.kernel.wireless.general/104602>
>
> Same situation is here - i have problem on Ivy Bridge.
(Note: I don't have any Ivy Bridge system. Just Sandy Bridge
and AMD's new A6-1450 Temash and both xhci work. So I can't
do any proper comparisons like you.)
> Steps to reproduce:
> - plug adapter. Module and firmware will be loaded
> - make sure usb autosupend is enabled. By default it is not! Use
> powertop or directly sysfs to enable autosuspend for this device
> - rmmod .... and wait some seconds until adapter is suspended and then
> modprobe ath9k_htc
>
> first packet which is bigger as 64Byte will kill EP4 FIFO. Size register
> will report wrong size.. bigger as FIFO can handle. And only first ~40
> readet bytes will be actually OK.. all the rest of packet will be trashed.
This is what happens with a WN721 (ar9271):
[17619.597905] usbcore: deregistering interface driver ath9k_htc
[17619.679549] usb 2-2: ath9k_htc: USB layer deinitialized
[17619.679602] ath9k_htc: Driver unloaded
<suspend>
<resume>
[17667.543024] usb 2-2: reset high-speed USB device number 3 using xhci_hcd <----
[17667.572168] xhci_hcd 0000:19:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88031aa77600
[17667.572174] xhci_hcd 0000:19:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88031aa77640
[17667.572177] xhci_hcd 0000:19:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88031aa77680
[17667.572180] xhci_hcd 0000:19:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88031aa776c0
[17667.572183] xhci_hcd 0000:19:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88031aa77700
[17667.572185] xhci_hcd 0000:19:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88031aa77740
[17667.573826] usb 2-2: ath9k_htc: Firmware htc_9271.fw requested
[17667.573873] usbcore: registered new interface driver ath9k_htc
[17668.038200] usb 2-2: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
[17668.273249] ath9k_htc 2-2:1.0: ath9k_htc: HTC initialized with 33 credits
The driver loads, but there's no "wlanX" interface, no phyX interface
and the driver can't be unloaded due to "Error: Module ath9k_htc is in use".
Regards
Christian
next prev parent reply other threads:[~2013-07-22 21:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51ED4E12.8030006@rempel-privat.de>
2013-07-22 19:54 ` FUSB200 xhci issue Christian Lamparter
2013-07-22 20:47 ` Oleksij Rempel
2013-07-22 21:23 ` Christian Lamparter [this message]
2013-07-23 4:59 ` Oleksij Rempel
2013-07-23 18:26 ` Christian Lamparter
2013-07-24 10:37 ` Oleksij Rempel
2013-07-27 21:59 ` Christian Lamparter
2013-07-28 5:50 ` Oleksij Rempel
2013-07-28 11:38 ` Christian Lamparter
2013-07-28 12:12 ` Oleksij Rempel
2013-07-28 14:28 ` Oleksij Rempel
2013-07-28 20:41 ` Christian Lamparter
2013-07-31 6:52 ` Oleksij Rempel
2013-08-08 15:35 ` Oleksij Rempel
2013-08-08 19:09 ` Christian Lamparter
2013-08-08 20:19 ` Alan Stern
2013-08-08 22:06 ` Christian Lamparter
2013-08-09 2:52 ` Sujith Manoharan
2013-08-09 14:32 ` ath9k_htc firmware problem [was: Re: FUSB200 xhci issue] Alan Stern
2013-08-09 14:13 ` FUSB200 xhci issue Alan Stern
2013-08-09 14:34 ` Oleksij Rempel
2013-08-09 14:52 ` Alan Stern
2013-08-09 15:51 ` Oleksij Rempel
2013-08-09 17:16 ` Alan Stern
2013-08-09 18:53 ` Oleksij Rempel
2013-08-09 19:32 ` Alan Stern
2013-08-10 6:19 ` Oleksij Rempel
2013-08-10 11:57 ` Alan Stern
2013-08-12 7:58 ` 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=3155156.7uKpoiQrxp@blech \
--to=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=sarah.a.sharp@linux.intel.com \
--cc=seth.forshee@canonical.com \
/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).