RE: usb3 express card: unable to enumerate USB device

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

 



> -----Original Message-----
> From: linux-usb-owner@xxxxxxxxxxxxxxx [mailto:linux-usb-
> owner@xxxxxxxxxxxxxxx] On Behalf Of CAI Qian
> Sent: Wednesday, July 20, 2011 3:36 PM
> To: linux-usb
> Cc: Sarah Sharp
> Subject: usb3 express card: unable to enumerate USB device
> 
> Hi Sarah and all,
> 
> While debugging https://bugzilla.kernel.org/show_bug.cgi?id=34782,
> there are many of those messages after the reboot.
> 
> usb 9-2: new high speed USB device number 3 using xhci_hcd
> xhci_hcd 0000:05:00.0: ERROR: unexpected command completion code 0x0.
> xhci_hcd 0000:05:00.0: ERROR: unexpected command completion code 0x0.
> usb 9-2: device not accepting address 3, error -22
> usb 9-2: new high speed USB device number 4 using xhci_hcd
> xhci_hcd 0000:05:00.0: ERROR: unexpected command completion code 0x0.
> xhci_hcd 0000:05:00.0: ERROR: unexpected command completion code 0x0.
> usb 9-2: device not accepting address 4, error -22
> usb 9-2: new high speed USB device number 5 using xhci_hcd
> xhci_hcd 0000:05:00.0: ERROR: unexpected command completion code 0x0.
> xhci_hcd 0000:05:00.0: ERROR: unexpected command completion code 0x0.
> usb 9-2: device not accepting address 5, error -22
> usb 9-2: new high speed USB device number 6 using xhci_hcd
> xhci_hcd 0000:05:00.0: ERROR: unexpected command completion code 0x0.
> xhci_hcd 0000:05:00.0: ERROR: unexpected command completion code 0x0.
> usb 9-2: device not accepting address 6, error -22
> hub 9-0:1.0: unable to enumerate USB device on port 2
> 
> 0000:05:00.0 is the Express Card USB 3.0 card.
> # lspci
> 05:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host
> Controller (rev 03)
> 
> From lsusb, there is no usb 9-2 but usb 9-1. I guess 9-2 is one of end
> port from
> the root hub of the Express Card.
> # lsusb
> Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> 
> As the results, the end device - USB 2 MP3 (9-3?) device could not be
> detected
> until re-attached. Does it look like a hardware or software problem?
> Any way to
> debug this enumeration problem any further?
> 

>From the log, it appears driver sends set address command to the host,
but the host returns a command completion TRB with completion code set
to 0, which means invalid. Sounds like a HW/FW problem to me.

Thanks,
Andiry
��.n��������+%������w��{.n�����{���)��jg��������ݢj����G�������j:+v���w�m������w�������h�����٥



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

  Powered by Linux