On Mon, Apr 08, 2002, Morgan Collins <[EMAIL PROTECTED]> wrote: > On Mon, 2002-04-08 at 16:26, Johannes Erdfelt wrote: > You're using usb-uhci, not uhci. If you're bored, it could be worth the > effort to try the uhci driver as well, but the code that handles > interrupts is similar enough that I don't think it'll make a difference. > > If you do try, can you cut and paste the portion of the log (dmesg) when > you plug in a device? > > Hmm, actually no.. lsmod says:
No, you're right. > My other PIIX4 shows usb-uhci in /proc/interrupts as well... so... looks > like a typo/thinko someplace, it's irrelivant in any case. Yeah, that was changed at one point and still confuses me. > Here is the log: > Apr 8 16:28:33 fury kernel: usb.c: registered new driver usbdevfs > Apr 8 16:28:33 fury kernel: usb.c: registered new driver hub > Apr 8 16:28:36 fury kernel: uhci.c: USB Universal Host Controller > Interface driver v1.1 > Apr 8 16:28:36 fury kernel: PCI: Found IRQ 10 for device 00:01.2 > Apr 8 16:28:36 fury kernel: uhci.c: USB UHCI at I/O 0xfce0, IRQ 10 > Apr 8 16:28:37 fury kernel: usb.c: new USB bus registered, assigned bus > number 1 > Apr 8 16:28:37 fury kernel: hub.c: USB hub found > Apr 8 16:28:37 fury kernel: hub.c: 2 ports detected > Apr 8 16:28:37 fury kernel: hub.c: USB new device connect on bus1/1, > assigned device number 2 > Apr 8 16:28:37 fury kernel: uhci.c: fce0: host system error, PCI > problems? > Apr 8 16:28:41 fury kernel: usb_control/bulk_msg: timeout > Apr 8 16:28:41 fury kernel: usb.c: USB device not accepting new > address=2 (error=-110) > Apr 8 16:28:42 fury kernel: hub.c: USB new device connect on bus1/1, > assigned device number 3 > Apr 8 16:28:46 fury kernel: usb_control/bulk_msg: timeout > Apr 8 16:28:46 fury kernel: usb.c: USB device not accepting new > address=3 (error=-110) Hmm, that HSE error is not good. That error is generated on a PCI Parity error, PCI Master Abort or PCI Target Abort. Sounds like the PCI side of the device wasn't setup correctly. That's not really our side of the kernel. You may want to try 2.5 since I believe there has been some PCI changes. You can also bring up the issue on the linux-kernel list where the PCI developers are. This could also be a bug in the HCD (uhci.o) so please try usb-uhci.o first. If they both have problems, then it's most likely a PCI setup problem. JE _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users Sponsored by http://www.ThinkGeek.com/
