https://bugzilla.novell.com/show_bug.cgi?id=681068 https://bugzilla.novell.com/show_bug.cgi?id=681068#c0 Summary: Kingston HyperXMax3.0 128GB flash drive not recognized Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: 32bit OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: Olaf.Amm@fmi.fi QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=420342) --> (http://bugzilla.novell.com/attachment.cgi?id=420342) Full boot.msg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Firefox/3.6.15 ( .NET CLR 3.5.30729) When I boot up openSuSE 11.4, or after booting attach my Kingston HyperXMax3.0 128GB USB3.0 flash drive, the drive does not get recognized, and nothing is seen in the device notifier. It is thus also not available in file managers etc. The drive anyhow shows a blue light which indicates a USB3.0 mode connection. The drive is connected via a DeLock PCI-E USB 3.0 card. This is a double boot machine, and using Windows XP SP3 with the same hardware, the drive works fine in USB 3.0 mode. So this must be a problem with the Linux kernel. Latest kernel is installed. - Note: With openSuSE 11.3 and the same hardware, the same drive was seen in device notifier and available in file managers etc, however only in USB2.0 mode (drive shows green light). - Relevant (I think) lines of boot.msg (full boot.msg see attachment): <6>[ 6.843781] xhci_hcd 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 <7>[ 6.843804] xhci_hcd 0000:04:00.0: setting latency timer to 64 <6>[ 6.843809] xhci_hcd 0000:04:00.0: xHCI Host Controller <6>[ 6.843821] xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 8 <6>[ 6.859663] FDC 0 is a post-1991 82077 <6>[ 6.968768] xhci_hcd 0000:04:00.0: irq 17, io mem 0xfeafe000 <7>[ 6.968834] xhci_hcd 0000:04:00.0: irq 40 for MSI/MSI-X <7>[ 6.968838] xhci_hcd 0000:04:00.0: irq 41 for MSI/MSI-X <7>[ 6.968842] xhci_hcd 0000:04:00.0: irq 42 for MSI/MSI-X <4>[ 6.972115] usb usb8: No SuperSpeed endpoint companion for config 1 interface 0 <6>[ 6.972124] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003 <6>[ 6.972127] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1 <6>[ 6.972129] usb usb8: Product: xHCI Host Controller <6>[ 6.972134] usb usb8: Manufacturer: Linux 2.6.37.1-1.2-pae xhci_hcd <6>[ 6.972137] usb usb8: SerialNumber: 0000:04:00.0 <7>[ 6.972235] xHCI xhci_add_endpoint called for root hub <7>[ 6.972237] xHCI xhci_check_bandwidth called for root hub <6>[ 6.972278] hub 8-0:1.0: USB hub found <6>[ 6.972283] hub 8-0:1.0: 4 ports detected . . . <6>[ 7.172358] usb 8-2: new SuperSpeed USB device using xhci_hcd and address 2 <6>[ 7.182640] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06 <6>[ 7.182752] iTCO_wdt: Found a ICH8 or ICH8R TCO device (Version=2, TCOBASE=0x0860 <6>[ 7.182828] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) <4>[ 7.189930] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep <4>[ 7.190302] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep <4>[ 7.190677] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep <4>[ 7.191176] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep <6>[ 7.191309] usb 8-2: New USB device found, idVendor=11b0, idProduct=6398 <6>[ 7.191313] usb 8-2: New USB device strings: Mfr=3, Product=4, SerialNumber=5 <6>[ 7.191315] usb 8-2: Product: HyperX Max 3.0 <6>[ 7.191317] usb 8-2: Manufacturer: Kingston <6>[ 7.191319] usb 8-2: SerialNumber: 0026182C72650AC10FFF0080 . . . <3>[ 12.192479] usb 8-2: can't set config #1, error -110 Reproducible: Always Steps to Reproduce: 1. Start openSuSE 11.4 2. Attach Kingston HyperXMax3.0 128GB flash drive 3. Actual Results: nothing happens, drive not seen in device notifier, file managers etc. Expected Results: device notifier should see drive, pop up with options to show drive in file managers etc. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.