public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andiry Xu <andiry.xu@amd.com>
To: Richard Farina <sidhayn@gmail.com>
Cc: <sarah.a.sharp@linux.intel.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Question about error from xhci-hcd
Date: Tue, 7 Feb 2012 17:52:12 +0800	[thread overview]
Message-ID: <4F30F44C.8090603@amd.com> (raw)
In-Reply-To: <4F30BB0B.5060203@gmail.com>

On 02/07/2012 01:47 PM, Richard Farina wrote:
> I apologize but I am having the same issue reported in this thread in
> December
> 
> [ 5077.573181] xhci_hcd 0000:0a:00.0: ERROR no room on ep ring
> 
> I saw no resolution on this issue so I figured I'd step up and see if
> you needed an active tester who could reproduce the issue.
> 
> I am running Gentoo with a 3.2.2 kernel.  I am able to run any kernel
> version you need, including random git trees and custom patches.  If you
> have not solved this yet, please allow me to be your test monkey. If you
> have solved this already then sorry for harming the signal to noise
> ratio, I could not a find a later message then the one below.
> 

You can try andiry-ring-expansion branch on Sarah's xhci git tree. It
contains bugs and I'm trying to fix that, but you can have a try.

Thanks,
Andiry

> 
> 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 
> --
> 
> 



  reply	other threads:[~2012-02-07  9:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07  5:47 Question about error from xhci-hcd Richard Farina
2012-02-07  9:52 ` Andiry Xu [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2011-10-29 17:48 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

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=4F30F44C.8090603@amd.com \
    --to=andiry.xu@amd.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=sidhayn@gmail.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