Seeking insight here ... I append a kernel debug log,
against 2.3.99 pre4-5, showing something I observed
last night.  This is with a PIIX4 UHCI.

Regardless of whether this keyboard/hub is buggy or not,
there's at least one kernel problem that it's tweaking. 

Any insights into what's really happening?

- Dave


    modprobe usb-uhci

Apr 10 19:56:58 xenon kernel: usb-uhci.c: $Revision: 1.228 $ time 21:53:24
Apr  9 2000 
Apr 10 19:56:58 xenon kernel: usb-uhci.c: High bandwidth mode enabled 
Apr 10 19:56:58 xenon kernel: usb-uhci.c: Intel USB controller: setting
latency timer to 0 
Apr 10 19:56:58 xenon kernel: usb-uhci.c: USB UHCI at I/O 0xfca0, IRQ 11 
Apr 10 19:56:58 xenon kernel: usb-uhci.c: Detected 2 ports 
Apr 10 19:56:58 xenon kernel: usb.c: new USB bus registered, assigned bus
number 1 
Apr 10 19:56:58 xenon kernel: usb.c: USB new device connect, assigned device
number 1 
Apr 10 19:56:58 xenon kernel: hub.c: USB hub found 
Apr 10 19:56:58 xenon kernel: hub.c: 2 ports detected 

    device 2 is a camera that's usually plugged in there

Apr 10 19:56:59 xenon kernel: usb.c: USB new device connect, assigned device
number 2 
Apr 10 19:56:59 xenon kernel: usb.c: This device is not recognized by any
installed USB driver. 

    plug in hub/keyboard to the other root hub port

Apr 10 19:57:47 xenon kernel: usb.c: USB new device connect, assigned device
number 3 
Apr 10 19:57:47 xenon kernel: hub.c: USB hub found 
Apr 10 19:57:47 xenon kernel: hub.c: 3 ports detected 
Apr 10 19:57:48 xenon kernel: usb.c: USB new device connect, assigned device
number 4 
Apr 10 19:57:48 xenon kernel: keybdev.c: Adding keyboard: input0 
Apr 10 19:57:48 xenon kernel: input0: USB HID v1.00 Keyboard 

    looked at a few things with my usbdevfs bus browser,
    and quit; device #2 wouldn't show its config descriptor.

Apr 10 19:58:17 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 604 
Apr 10 19:58:17 xenon kernel: usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128
rq 6 len 73 ret -32 
    
    plugged a device in to left keyboard port.

    NOTE:  it had just worked fine in same port, no probs ... with
    two key differences:  (1) OHCI, (2) keyboard wasn't in root hub.

Apr 10 20:01:01 xenon kernel: usb.c: USB new device connect, assigned device
number 5 
Apr 10 20:01:01 xenon kernel: usb.c: This device is not recognized by any
installed USB driver. 
Apr 10 20:01:01 xenon kernel: usb-uhci.c: interrupt, status 2, frame# 702 
Apr 10 20:01:01 xenon kernel: usb-uhci-debug.h:   TD @ c68c6d60/068C6D60,
MaxLen=07 DT0 EP=0 Dev=3 PID=(SETUP) buf=08467880 
Apr 10 20:01:01 xenon kernel: usb-uhci-debug.h:     Len=07 e0 SPD Stalled
CRC/Timeo  
Apr 10 20:01:01 xenon kernel: usb-uhci-debug.h:     Link points to TD @
068c6f60, Breadth first 
Apr 10 20:01:01 xenon kernel: hub.c: get_hub_status failed 
Apr 10 20:01:02 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 204 
Apr 10 20:01:03 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 1372 
Apr 10 20:01:03 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 1472 
Apr 10 20:01:05 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 524 
Apr 10 20:01:05 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 676 
Apr 10 20:01:06 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 1856 
Apr 10 20:01:07 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 780 
Apr 10 20:01:08 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 372 
    
    OK, end of experiment.  "tail -40 kern.debug", notice some
    interrupts, start to read the "TD" thing ...

Apr 10 20:01:09 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 448 
Apr 10 20:01:09 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 1028 
Apr 10 20:01:09 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 1124 
Apr 10 20:01:10 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 148 
Apr 10 20:01:10 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 192 
Apr 10 20:01:15 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 468 
Apr 10 20:01:16 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 1344 
Apr 10 20:01:16 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 1476 
Apr 10 20:01:17 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 924 
Apr 10 20:01:18 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 64 
Apr 10 20:01:19 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 548 
    
    ... the disk drive started making a _very_ determined buzz ...

Apr 10 20:01:20 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 1572 
Apr 10 20:01:20 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 20 
Apr 10 20:01:21 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 180 
Apr 10 20:01:21 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 192 
Apr 10 20:01:22 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 1728 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 252 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 276 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 300 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 324 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 348 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 372 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 396 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 420 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 444 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 468 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 492 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 516 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 540 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 564 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 588 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 612 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 636 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 660 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 684 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 708 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 732 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 756 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 780 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 804 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 828 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 852 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 876 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 900 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 924 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 948 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 972 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 996 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 1020 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 1044 
Apr 10 20:01:23 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 1068 
Apr 10 20:01:24 xenon kernel: usb-uhci.c: interrupt, status 3, frame# 1092 

        [ about 70 Kbytes of similar messages deleted ]
 

    ... until I yanked the keybd cable off the UHCI controller

Apr 10 20:01:44 xenon kernel: usb.c: USB disconnect on device 3 
Apr 10 20:01:44 xenon kernel: usb.c: USB disconnect on device 4 
Apr 10 20:01:44 xenon kernel: keybdev.c: Removing keyboard: input0 
Apr 10 20:01:44 xenon kernel: usb.c: USB disconnect on device 5 

    The day before I'd seen a similar sort of logfile fillup
    with those devices, but using OHCI.  Details differed,
    but the keyboard interrupt endpoint seemed to be the root
    cause in that case ... as perhaps here, though I don't know
    the HID/keyboard/mouse/event subsystem at all.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to