On Mon, 19 Dec 2005, Len Brown wrote:

> If i remove ehci-hcd.ko from Linux-2..15-rc5 and then boot,

You mean, if you boot and then rmmod ehci-hcd?

> the USB keyboard and mouse work fine.  I wiggle the mouse
> and get interrupts in IRQ209:
> 
> r3000:~ # cat /proc/interrupts
>            CPU0
>   0:      34121    IO-APIC-edge  timer
>   1:         12    IO-APIC-edge  i8042
>   4:       1255    IO-APIC-edge  serial
>   8:          0    IO-APIC-edge  rtc
>   9:        147   IO-APIC-level  acpi
>  12:        119    IO-APIC-edge  i8042
>  14:      11386    IO-APIC-edge  ide0
>  15:        969    IO-APIC-edge  ide1
> 177:          4   IO-APIC-level  yenta, ohci1394
> 185:        515   IO-APIC-level  yenta, eth0
> 201:        403   IO-APIC-level  NVidia nForce3
> 209:       4012   IO-APIC-level  ohci_hcd:usb1
> 217:          0   IO-APIC-level  ohci_hcd:usb2
> NMI:        106
> LOC:      34064
> ERR:          0
> MIS:          0
> 
> 
> #modprobe ehci-hcd
> and the mouse and keyboard stop working, 
> but if I CTRL-ALT-BACKSPACE to restart X, they start working
> and I still see the interrupts on IRQ209:
> 
> r3000:~ # cat /proc/interrupts
>            CPU0
>   0:      73922    IO-APIC-edge  timer
>   1:         12    IO-APIC-edge  i8042
>   4:       1255    IO-APIC-edge  serial
>   8:          0    IO-APIC-edge  rtc
>   9:        279   IO-APIC-level  acpi
>  12:        119    IO-APIC-edge  i8042
>  14:      11925    IO-APIC-edge  ide0
>  15:       2391    IO-APIC-edge  ide1
> 177:          4   IO-APIC-level  yenta, ohci1394
> 185:       1452   IO-APIC-level  yenta, eth0
> 201:        403   IO-APIC-level  NVidia nForce3
> 209:       6618   IO-APIC-level  ohci_hcd:usb1, ehci_hcd:usb3
> 217:          0   IO-APIC-level  ohci_hcd:usb2
> NMI:        110
> LOC:      73867
> ERR:          0
> MIS:          0

For problems like this, it's best not to run X during testing.  In 
addition to whatever USB problems there may be, X adds a whole new set of 
issues by interacting in strange ways with the input layer.  Better to do 
your testing in a VT console.

If everything works outside of X, then probably it's a matter of adjusting 
your X configuration file.

> #rmmod ohci-hcd
> and the mouse and keyboard keep working:
> 
> r3000:~ # cat /proc/interrupts
>            CPU0
>   0:     184941    IO-APIC-edge  timer
>   1:         12    IO-APIC-edge  i8042
>   4:       1255    IO-APIC-edge  serial
>   8:          0    IO-APIC-edge  rtc
>   9:        645   IO-APIC-level  acpi
>  12:        119    IO-APIC-edge  i8042
>  14:      14861    IO-APIC-edge  ide0
>  15:       6333    IO-APIC-edge  ide1
> 177:          4   IO-APIC-level  yenta, ohci1394
> 185:       2657   IO-APIC-level  yenta, eth0
> 201:        828   IO-APIC-level  NVidia nForce3
> 209:      13484   IO-APIC-level  ehci_hcd:usb3
> NMI:        143
> LOC:     184890
> ERR:          0
> MIS:          0
> 
> So it seems that either ehci-hcd or ohci-hcd will work, but
> not so well together.

Above you said they did work together, after you had restarted X.

If you turn on CONFIG_USB_DEBUG, the dmesg log will provide more 
information.  Also, it would help to see your /proc/bus/usb/devices with 
the mouse & keyboard plugged in.

Alan Stern



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to