Re: Problem with xHCI; mass storage device not detected

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/09/2012 08:15 AM, Sarah Sharp wrote:
> On Wed, Feb 08, 2012 at 02:28:36PM -0800, Sarah Sharp wrote:
>> On Thu, Feb 02, 2012 at 02:14:20AM +0200, Felipe Contreras wrote:
>>> On Wed, Feb 1, 2012 at 6:51 PM, Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx> wrote:
>>>> On Tue, Jan 31, 2012 at 10:52:42PM +0200, Felipe Contreras wrote:
>>>>> Note that this USB 2.0 device didn't work =/
>>
>> Yep, I see that the host controller doesn't like some input we gave it
>> when we tried to set up the configuration endpoint rings:
>>
>> Jan 31 22:43:53 dyfed kernel: [   79.045933] xhci_hcd 0000:02:00.0: ERROR: unexpected command completion code 0x11.
>> Jan 31 22:43:53 dyfed kernel: [   79.045935] xhci_hcd 0000:02:00.0: xhci_reset_bandwidth called for udev ffff88042bec7000
>> Jan 31 22:43:53 dyfed kernel: [   79.045936] xhci_hcd 0000:02:00.0: Freeing ring at ffff880429dceae0
>> Jan 31 22:43:53 dyfed kernel: [   79.045937] xhci_hcd 0000:02:00.0: Freeing DMA segment at ffff88000282b800 (virtual) 0x282b800 (DMA)
>> Jan 31 22:43:53 dyfed kernel: [   79.045939] xhci_hcd 0000:02:00.0: Freeing priv segment structure at ffff88042bee91c0
>> Jan 31 22:43:53 dyfed kernel: [   79.045943] xhci_hcd 0000:02:00.0: Freeing ring at ffff880429dce060
>> Jan 31 22:43:53 dyfed kernel: [   79.045944] xhci_hcd 0000:02:00.0: Freeing DMA segment at ffff880002843000 (virtual) 0x2843000 (DMA)
>> Jan 31 22:43:53 dyfed kernel: [   79.045946] xhci_hcd 0000:02:00.0: Freeing priv segment structure at ffff88042bee9fe0
>>
>> I'll have to look at the input and see what we're doing wrong.
> 
> Ok, I'm really not sure what's going wrong here.  The host controller is
> rejecting the configure endpoint command with a completion code of 0x11,
> which is a parameter error.  But I've double checked the input context,
> and everything looks correct, according to the 0.96 xHCI spec.  That
> checking is attached.
> 

Doesn't the Interval field of ep_info looks suspicious? The value is
0xff, while spec says the legal range is 3 to 11 for Full/Low speed
interrupt eps and 0 to 15 for all other endpoint types.

Thanks,
Andiry

> Do any USB 2.0 devices work under this host controller?  Maybe something
> that has a different endpoint type than a bulk endpoint, like a webcam
> or mouse?
> 
> Sarah Sharp


--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux