From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k-htc on OHCI -> bogus usb xfer
Date: Tue, 5 Jul 2016 12:20:08 +0000 [thread overview]
Message-ID: <1467721137.3144.81.camel@synopsys.com> (raw)
Hello,
Looks like this is another manifestation of already seen problem with ath9k-htc
and OHCI controller.
I'm trying to get USB Wi-Fi dongle based on Atheros AR9271 to work with our
development board (this is Synopsys AXS103) and seeing a picture very similar to
what was discussed here+AKA-http://thread.gmane.org/gmane.linux.usb.general/110847
Below is what I see on insertion of the dongle.
Note I have the most recent ath9k-htc firmware (see +ACI-ath9k+AF8-htc/htc+AF8-9271-1.4.0.fw+ACI-
in the log below) and Linux kernel is 4.6.3 (latest stable as of today) but the same
happens even on 4.4.
Interesting enough if I simply remove or disable the warning like that
------------------------+AD4-8---------------------------
diff --git a/drivers/usb/core/urb.c b/drivers/usb/core/urb.c
index 3d27477..a317e1e 100644
--- a/drivers/usb/core/urb.c
+-+-+- b/drivers/usb/core/urb.c
+AEAAQA- -443,11 +-443,6 +AEAAQA- int usb+AF8-submit+AF8-urb(struct urb +ACo-urb, gfp+AF8-t mem+AF8-flags)
+AKAAoACgAKAAoACgAKAAoACgACo- cause problems in HCDs if they get it wrong.
+AKAAoACgAKAAoACgAKAAoACgACo-/
+AKA-
-+AKAAoACgAKAAoACgAKA-/+ACo- Check that the pipe's type matches the endpoint's type +ACo-/
-+AKAAoACgAKAAoACgAKA-if (usb+AF8-pipetype(urb-+AD4-pipe) +ACEAPQ- pipetypes+AFs-xfertype+AF0-)
-+AKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACg-dev+AF8-WARN(+ACY-dev-+AD4-dev, +ACI-BOGUS urb xfer, pipe +ACU-x +ACEAPQ- type +ACU-x+AFw-n+ACI-,
-+AKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoA-usb+AF8-pipetype(urb-+AD4-pipe), pipetypes+AFs-xfertype+AF0-)+ADs-
-
+AKAAoACgAKAAoACgAKAAoA-/+ACo- Check against a simple/standard policy +ACo-/
+AKAAoACgAKAAoACgAKAAoA-allowed +AD0- (URB+AF8-NO+AF8-TRANSFER+AF8-DMA+AF8-MAP +AHw- URB+AF8-NO+AF8-INTERRUPT +AHw- URB+AF8-DIR+AF8-MASK +AHw-
+AKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACgAKAAoACg-URB+AF8-FREE+AF8-BUFFER)+ADs-
------------------------+AD4-8---------------------------
everything seem to work quite nice.
Any thoughts are much appreciated.
That's the log itself:
------------------------+AD4-8---------------------------
usb 1-1: new full-speed USB device number 2 using ohci-platform
usb 1-1: ath9k+AF8-htc: Firmware ath9k+AF8-htc/htc+AF8-9271-1.4.0.fw requested
usb 1-1: ath9k+AF8-htc: Transferred FW: ath9k+AF8-htc/htc+AF8-9271-1.4.0.fw, size: 51008
------------+AFs- cut here +AF0-------------
WARNING: CPU: 0 PID: 4 at drivers/usb/core/urb.c:450 usb+AF8-submit+AF8-urb+-0x162/0x404
usb 1-1: BOGUS urb xfer, pipe 1 +ACEAPQ- type 3
Modules linked in:
CPU: 0 PID: 4 Comm: kworker/0:0 Not tainted 4.6.3 +ACM-10
Workqueue: events request+AF8-firmware+AF8-work+AF8-func
Stack Trace:
+AKA- arc+AF8-unwind+AF8-core.constprop.1+-0x94/0x10c
---+AFs- end trace 2249b79eac9991d1 +AF0----
------------+AFs- cut here +AF0-------------
WARNING: CPU: 0 PID: 4 at drivers/usb/core/urb.c:450 usb+AF8-submit+AF8-urb+-0x162/0x404
usb 1-1: BOGUS urb xfer, pipe 1 +ACEAPQ- type 3
Modules linked in:
CPU: 0 PID: 4 Comm: kworker/0:0 Tainted: G+AKAAoACgAKAAoACgAKAAoA-W+AKAAoACgAKAAoACgAKA-4.6.3 +ACM-10
Workqueue: events request+AF8-firmware+AF8-work+AF8-func
Stack Trace:
+AKA- arc+AF8-unwind+AF8-core.constprop.1+-0x94/0x10c
---+AFs- end trace 2249b79eac9991d2 +AF0----
------------+AFs- cut here +AF0-------------
WARNING: CPU: 0 PID: 4 at drivers/usb/core/urb.c:450 usb+AF8-submit+AF8-urb+-0x162/0x404
usb 1-1: BOGUS urb xfer, pipe 1 +ACEAPQ- type 3
Modules linked in:
CPU: 0 PID: 4 Comm: kworker/0:0 Tainted: G+AKAAoACgAKAAoACgAKAAoA-W+AKAAoACgAKAAoACgAKA-4.6.3 +ACM-10
Workqueue: events request+AF8-firmware+AF8-work+AF8-func
Stack Trace:
+AKA- arc+AF8-unwind+AF8-core.constprop.1+-0x94/0x10c
---+AFs- end trace 2249b79eac9991d3 +AF0----
...
------------------------+AD4-8---------------------------
-Alexey
next reply other threads:[~2016-07-05 12:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 12:20 Alexey Brodkin [this message]
2016-07-05 17:23 ` [ath9k-devel] ath9k-htc on OHCI -> bogus usb xfer Oleksij Rempel
2016-07-05 17:31 ` Alexey Brodkin
2016-07-05 19:01 ` Oleksij Rempel
2016-07-06 7:44 ` Alexey Brodkin
2016-07-06 8:30 ` fixed-term.Oleksij.Rempel
2016-07-06 8:32 ` Alexey Brodkin
2016-07-06 8:39 ` fixed-term.Oleksij.Rempel
2016-07-06 8:45 ` Alexey Brodkin
2016-07-06 9:09 ` fixed-term.Oleksij.Rempel
2016-07-06 9:30 ` Alexey Brodkin
2016-07-06 10:32 ` fixed-term.Oleksij.Rempel
2016-07-07 5:16 ` Alexey Brodkin
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=1467721137.3144.81.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).