On Sat, Jun 19, 2004, Markus Raab <[EMAIL PROTECTED]> wrote: > My 4 port usb card with the chip VT6202 works only with 2 Ports. My Kernel is > 2.6.7. > > Kernel messages: > Jun 18 16:41:01 superbyte kernel: PCI: Found IRQ 9 for device 0000:00:0c.2 > Jun 18 16:41:01 superbyte kernel: PCI: Sharing IRQ 9 with 0000:00:0a.0 > Jun 18 16:41:01 superbyte kernel: ehci_hcd 0000:00:0c.2: VIA Technologies, > Inc. USB 2.0 > Jun 18 16:41:01 superbyte kernel: ehci_hcd 0000:00:0c.2: irq 9, pci mem > d8961f00 > Jun 18 16:41:01 superbyte kernel: ehci_hcd 0000:00:0c.2: new USB bus > registered, assigned bus number 4 > Jun 18 16:41:01 superbyte kernel: ehci_hcd 0000:00:0c.2: USB 2.0 enabled, EHCI > 0.95, driver 2004-May-10 > Jun 18 16:41:01 superbyte kernel: hub 4-0:1.0: USB hub found > Jun 18 16:41:01 superbyte kernel: hub 4-0:1.0: 4 ports detected > Jun 18 16:41:01 superbyte kernel: hub 4-0:1.0: over-current change on port 3 > Jun 18 16:41:01 superbyte kernel: hub 4-0:1.0: over-current change on port 4 > > Port 3 and 4 are not working. > > /proc/interrupts: > 9: 144510 XT-PIC EMU10K1, ehci_hcd > but also when rmmod the emu10k1 (means unshared irq?) the same problem > accours. > > /proc/iomem: > efffff00-efffffff : 0000:00:0c.2 > efffff00-efffffff : ehci_hcd > > lspci: > 0000:00:0c.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51) (prog-if > 20 [EHCI]) > Subsystem: VIA Technologies, Inc. (Wrong ID): Unknown device 1234 > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- > Stepping- SERR- FastB2B- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- > Latency: 64, Cache Line Size: 0x10 (64 bytes) > Interrupt: pin C routed to IRQ 9 > Region 0: Memory at efffff00 (32-bit, non-prefetchable) > Capabilities: [80] Power Management version 2 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0 > +,D1-,D2-,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > > I would be glad to hear from you, independantly if you want more info or have > an idea how to patch the problem.
You seem pretty sure this is a bug in the hub driver. What makes you think it's not a hardware problem? JE ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
