On Wed, 4 Mar 2009, Yegor Yefremov wrote: > Greetings, > > I'm porting 2.6.29 to our ARM9 (Micrel KS8695) based box. For USB > connections VIA VT6212 controller is attached to the PCI bus. If > connecting a card reader I get following error message concerning no-IRQ: > > ehci_hcd 0000:00:06.2: port 2 high speed > ehci_hcd 0000:00:06.2: GetStatus port 2 status 001005 POWER sig=se0 PE > CONNECT > usb 1-2: new high speed USB device using ehci_hcd and address 2 > usb usb2: suspend_rh (auto-stop) > usb usb3: suspend_rh (auto-stop) > ------------------------------------------------------------------------------------------- > ehci_hcd 0000:00:06.2: Unlink after no-IRQ? Controller is probably using > the wrong IRQ. > ------------------------------------------------------------------------------------------- This message may be right. Are you getting any interrupts from your EHCI controller? > usb 1-2: khubd timed out on ep0in len=18/64 > ehci_hcd 0000:00:06.2: port 2 high speed > ehci_hcd 0000:00:06.2: GetStatus port 2 status 001005 POWER sig=se0 PE > CONNECT > usb usb2: uevent > usb 2-0:1.0: uevent > usb usb3: uevent > usb 3-0:1.0: uevent > usb usb1: uevent > usb 1-0:1.0: uevent > usb 1-2: khubd timed out on ep0out len=0/0 > udev: renamed network interface wlan0 to wlan1 > usb 1-2: khubd timed out on ep0out len=0/0 > usb 1-2: device not accepting address 2, error -110 > ehci_hcd 0000:00:06.2: port 2 high speed > ehci_hcd 0000:00:06.2: GetStatus port 2 status 001005 POWER sig=se0 PE > CONNECT > usb 1-2: new high speed USB device using ehci_hcd and address 3 > usb 1-2: khubd timed out on ep0in len=18/64 > ehci_hcd 0000:00:06.2: port 2 high speed > ehci_hcd 0000:00:06.2: GetStatus port 2 status 001005 POWER sig=se0 PE > CONNECT > usb 1-2: khubd timed out on ep0out len=0/0 > usb 1-2: khubd timed out on ep0out len=0/0 > usb 1-2: device not accepting address 3, error -110 > ehci_hcd 0000:00:06.2: port 2 high speed > ehci_hcd 0000:00:06.2: GetStatus port 2 status 001005 POWER sig=se0 PE > CONNECT > usb 1-2: new high speed USB device using ehci_hcd and address 4 > usb 1-2: khubd timed out on ep0out len=0/0 > usb 1-2: khubd timed out on ep0out len=0/0 > usb 1-2: device not accepting address 4, error -110 > ehci_hcd 0000:00:06.2: port 2 high speed > ehci_hcd 0000:00:06.2: GetStatus port 2 status 001005 POWER sig=se0 PE > CONNECT > usb 1-2: new high speed USB device using ehci_hcd and address 5 > usb 1-2: khubd timed out on ep0out len=0/0 > usb 1-2: khubd timed out on ep0out len=0/0 > usb 1-2: device not accepting address 5, error -110 > hub 1-0:1.0: unable to enumerate USB device on port 2 > hub 2-0:1.0: state 7 ports 2 chg 0000 evt 0000 > hub 3-0:1.0: state 7 ports 2 chg 0000 evt 0000 > usb usb2: wakeup_rh (auto-start) > hub 2-0:1.0: state 7 ports 2 chg 0000 evt 0004 > uhci_hcd 0000:00:06.0: port 2 portsc 0093,00 > hub 2-0:1.0: port 2, status 0101, change 0001, 12 Mb/s > hub 2-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x101 > usb 2-2: new full speed USB device using uhci_hcd and address 2 > usb 2-2: not running at top speed; connect to a high speed hub > usb 2-2: default language 0x0409 > usb 2-2: New USB device found, idVendor=058f, idProduct=6362 > usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > usb 2-2: Product: Mass Storage Device > usb 2-2: Manufacturer: Generic > usb 2-2: SerialNumber: 058F312D81B > usb 2-2: uevent > usb 2-2: usb_probe_device > usb 2-2: configuration #1 chosen from 1 choice > usb 2-2: adding 2-2:1.0 (config #1, interface 0) > usb 2-2:1.0: uevent > usb-storage 2-2:1.0: usb_probe_interface > > after that the card is correctly detected and I can mount and browse my > CF card. But all interactions with the card reader are going very > slowly, as if interrupts were disabled. Or as if the card is connected to a full-speed UHCI controller (which it is! -- look above) instead of the EHCI controller. > There were no such problem with 2.6.24 kernel. Our box uses two kernels: > > 1.â??BIOSâ?? kernel: will be started from internal 4Mb flash > 2.â??Finalâ?? kernel on external medium (to run final OS like Debian etc.). > This kernel will be started via kexec > Our BIOS kernel is 2.6.24, if the final kernel is 2.6.29 then I > experience no problems. But if I update BIOS kernel to 2.6.29 I have the > above described behavior. It looks like the VT6212 chip is initialized > correctly via 2.6.24 kernel. > > Any idea what could be wrong? You should check the interrupt routing. 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
