From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: USB list <linux-usb@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, v4mp <gaigo88@hotmail.it>
Subject: Re: Question about error from xhci-hcd
Date: Sun, 30 Oct 2011 06:04:43 +0100 [thread overview]
Message-ID: <20111030050443.GC4535@xanatos> (raw)
In-Reply-To: <4EAC3C5C.5000209@lwfinger.net>
On Sat, Oct 29, 2011 at 12:48:12PM -0500, Larry Finger wrote:
> Sarah,
>
> Pardon the intrusion, but I'm trying to fix a problem for v4mp, a
> user of the rtl8192cu driver on an Alfa AWUS036NHR. I have one of
> the devices, and it works on a USB 2.0 hub, but fails with 3.0
> hardware with lots of
>
> xhci_hcd 0000:05:00.0: ERROR no room on ep ring
>
> messages logged.
The xHCI driver allocates a fixed-size endpoint ring, and only so much
data can fit on it. If the driver is allocating many URBs or many URBs
with a lot of data, then you will see these messages and the URBs will
fail to be submitted. Now if neither of those conditions are true, then
it's possible we just have a bug in the xHCI driver.
There is a patchset in the works to dynamically expand the endpoint
rings, but it's still going through revisions:
http://marc.info/?l=linux-usb&m=131918645424329&w=2
It might be done for the 3.3 kernel, but until then the driver is just
going to be broken, sorry. :(
> The device works with an out-of-kernel driver available from the
> Alfa or Realtek web sites, but I want to fix rtl8192cu.
>
> What condition leads to the above message? The user's dmesg buffer
> has wrapped, thus I don't see the beginning of the failure. He is
> using a canned distro kernel, thus he cannot include any extra
> debugging info such as a stack dump when the errors occur. As he
> uses the compat-wireless package, I think I can incorporate a new
> copy of xhci-hcd with it, but I have not done so yet.
Which distro? Several of the distros are based on 2.6.32, which only
had minimal support for xHCI. Updating just the xHCI driver with a
more recent one isn't going to be possible with that old of a kernel,
since later changes also touched the USB core as well.
Sarah Sharp
next prev parent reply other threads:[~2011-10-30 5:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 17:48 Question about error from xhci-hcd Larry Finger
2011-10-30 5:04 ` Sarah Sharp [this message]
2011-10-30 15:30 ` Larry Finger
2011-11-01 16:06 ` Larry Finger
2011-11-14 9:18 ` Andiry Xu
2011-11-28 18:14 ` Sarah Sharp
2011-11-28 21:53 ` Larry Finger
2011-12-28 16:30 ` Larry Finger
2011-12-29 3:32 ` Andiry Xu
2011-12-29 3:55 ` Larry Finger
2011-12-29 4:30 ` Andiry Xu
2011-12-29 16:49 ` Larry Finger
-- strict thread matches above, loose matches on Subject: below --
2012-02-07 5:47 Richard Farina
2012-02-07 9:52 ` Andiry Xu
2012-02-07 13:30 ` Larry Finger
2012-02-07 14:55 ` Sarah Sharp
2012-02-07 19:28 ` Larry Finger
2012-02-07 14:59 ` Richard Farina
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=20111030050443.GC4535@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gaigo88@hotmail.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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