On Tue, 12 Mar 2013, Huang Rui wrote: > Hi Alan, > > The same problem is encountered in my side. Bruce's log doesn't > demonstrate the break point. I attached a new one. > > [ 14.359603] hub 1-0:1.0: state 7 ports 4 chg 0004 evt 0000 > [ 14.359613] hub 1-0:1.0: port 2, status 0101, change 0000, 12 Mb/s > [ 14.385538] ohci_hcd 0000:00:12.0: port[1] reset timeout, stat 00000111 > [ 14.431601] hub 3-0:1.0: port 2: status 0101 change 0001 > [ 14.435601] hub 4-0:1.0: port 2: status 0203 change 0001 > [ 14.439596] ohci_hcd 0000:00:12.0: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS > [ 14.495599] usb 1-2: new full-speed USB device number 2 using ohci_hcd > [ 14.521546] ohci_hcd 0000:00:12.0: port[1] reset timeout, stat 00000113 > [ 14.575610] ohci_hcd 0000:00:12.0: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS > [ 14.656656] usb 1-2: Parent hub missing LPM exit latency info. Power management will be impacted. > [ 14.658656] usb 1-2: not running at top speed; connect to a high speed hub > [ 14.664658] usb 1-2: default language 0x0409 > [ 14.670658] usb 1-2: udev 2, busnum 1, minor = 1 > [ 14.670660] usb 1-2: New USB device found, idVendor=05e3, idProduct=0732 > [ 14.670662] usb 1-2: New USB device strings: Mfr=3, Product=4, SerialNumber=5 > [ 14.670664] usb 1-2: Product: USB Reader > [ 14.670666] usb 1-2: Manufacturer: Genesys > [ 14.670668] usb 1-2: SerialNumber: 000000000038 That is not the relevant part of the log. Here's the important part: [ 28.924735] ehci-pci 0000:00:12.2: GetStatus port:2 status 001803 0 ACK POWER sig=j CSC CONNECT [ 28.924739] hub 5-0:1.0: port 2: status 0501 change 0001 ... [ 30.352837] ehci-pci 0000:00:12.2: port 2 full speed --> companion This shows that the card reader did attach to the EHCI controller, but then failed to indicate that it was capable of high-speed operation. I have no idea why not. Can you use git bisect to find the commit responsible for this? Alan Stern -- 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
