From: Larry Finger <Larry.Finger@lwfinger.net>
To: Andiry Xu <andiry.xu@amd.com>
Cc: Sarah Sharp <sarah.a.sharp@linux.intel.com>,
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: Thu, 29 Dec 2011 10:49:33 -0600 [thread overview]
Message-ID: <4EFC9A1D.4000601@lwfinger.net> (raw)
In-Reply-To: <4EFBECE1.2060001@amd.com>
On 12/28/2011 10:30 PM, Andiry Xu wrote:
>
> That's the error I want to see, but I didn't find it in the dmesg you
> posted. is it wrapped?
>
> Anyway, please post the full dmesg with no room on ring error and the
> dump of the ep ring and event ring (so the xhci_debug_ring() is
> triggered in the patch), so we can see if the ring is mangled or there
> is just too many transfers.
>
> Another thing you can try is the andiry-ring-expansion branch on Sarah's
> xhci git tree, check if there is still no room on ring error.
No, the ring is not wrapped. I seems that my anti-spam mechanism kicked in too
soon. or the run stopped too soon.
I'll have the OP do another run and see if we can get the right information.
Larry
next prev parent reply other threads:[~2011-12-29 16:49 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
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 [this message]
-- 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=4EFC9A1D.4000601@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=andiry.xu@amd.com \
--cc=gaigo88@hotmail.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.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