Hide Forgot
Dear Support, I bought an USB 3.0 PCMCIA (AOLT LT-232) and I can see it in my devices list (lsusb); Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 17ef:4807 Lenovo UVC Camera Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc. AES2810 Bus 004 Device 003: ID 0a5c:2145 Broadcom Corp. Bluetooth After attaching an external HD with an USB 3.0 interface I can see the following in the /var/log/messages: [15951.487710] pciehp 0000:00:1c.3:pcie04: Card not present on Slot(3) [15951.487872] xhci_hcd 0000:05:00.0: remove, state 1 [15951.487889] usb usb10: USB disconnect, device number 1 [15951.493126] pciehp 0000:00:1c.3:pcie04: Card present on Slot(3) [15951.507133] hub 10-0:1.0: hub_port_status failed (err = -19) [15956.507143] xhci_hcd 0000:05:00.0: Timeout while waiting for a slot [15956.507157] hub 10-0:1.0: couldn't allocate port 2 usb_device [15956.507359] xHCI xhci_drop_endpoint called for root hub [15956.507366] xHCI xhci_check_bandwidth called for root hub [15956.512368] xhci_hcd 0000:05:00.0: USB bus 10 deregistered [15956.513138] xhci_hcd 0000:05:00.0: remove, state 4 [15956.513152] usb usb9: USB disconnect, device number 1 [15956.513256] xHCI xhci_drop_endpoint called for root hub [15956.513261] xHCI xhci_check_bandwidth called for root hub [15956.517345] xhci_hcd 0000:05:00.0: USB bus 9 deregistered [15956.517535] xhci_hcd 0000:05:00.0: PCI INT A disabled After this the PCMCIA have to be removed and reinserted because I can't see it anymore in USB device list (lsusb); Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 004: ID 17ef:4807 Lenovo UVC Camera Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc. AES2810 Bus 004 Device 003: ID 0a5c:2145 Broadcom Corp. Bluetooth Using any other USB 2.0 device, all works correctly. How do you think about it? I'm running a fresh installed Fedora 16 and my kernel is 3.1.6-1.fc16.i686.PAE. USB Components Installed: libertas-usb8388-firmware-5.110.22.p23-5.fc15.noarch libusb1-1.0.9-0.3.rc1.fc16.i686 xorg-x11-drv-sisusb-0.9.4-7.fc16.i686 usbutils-003-4.fc16.i686 rt73usb-firmware-1.8-8.fc15.noarch libgusb-0.1.3-1.fc16.i686 usb_modeswitch-data-20111023-1.fc16.noarch usbmuxd-1.0.7-1.fc16.i686 usb_modeswitch-1.2.0-1.fc16.i686 libusb-0.1.3-9.fc16.i686 Thanks and regards, Luca
3.1 is fairly old. Are you still seeing this with the 3.4 or 3.5 kernel updates?
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.