Jiri, do you have any suggestions for further debugging? On Mon, 7 Feb 2011, kholis wrote: > Log messages is changed randomly. its show something like this: > > --unplugged message > Feb 7 09:55:19 kalau kernel: [ 295.178510] usb 2-1.1: USB > disconnect, address 6 > Feb 7 09:55:19 kalau kernel: [ 295.178515] usb 2-1.1.4: USB > disconnect, address 7 That's normal. > --plugged message (Lets called it: Message A) > Feb 7 09:55:22 kalau kernel: [ 297.932413] usb 2-1.1: new high speed > USB device using ehci_hcd and address 8 > Feb 7 09:55:22 kalau kernel: [ 298.025416] hub 2-1.1:1.0: USB hub found > Feb 7 09:55:22 kalau kernel: [ 298.025601] hub 2-1.1:1.0: 4 ports detected > Feb 7 09:55:23 kalau kernel: [ 298.295496] usb 2-1.1.4: new full > speed USB device using ehci_hcd and address 9 > Feb 7 09:55:23 kalau kernel: [ 298.392999] input: Keytouch as QWERTY > Panel as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1.4/2-1.1.4:1.0/input/input9 > Feb 7 09:55:23 kalau kernel: [ 298.393253] generic-usb > 0003:0926:3333.0003: input,hidraw1: USB HID v1.10 Keyboard [Keytouch > as QWERTY Panel] on usb-0000:00:1d.0-1.1.4/input0 That's also normal. Obviously the patch helped; you never got this much information before. > --unplugged message > Feb 7 10:05:18 kalau kernel: [ 892.676271] usb 2-1.1: USB > disconnect, address 8 > Feb 7 10:05:18 kalau kernel: [ 892.676278] usb 2-1.1.4: USB > disconnect, address 9 > Feb 7 10:05:18 kalau kernel: [ 892.676384] > drivers/hid/usbhid/hid-core.c: can't reset device, > 0000:00:1d.0-1.1.4/input0, status -108 That's normal too. > --plugged message > Feb 7 10:05:43 kalau kernel: [ 917.919665] usb 2-1.1: new high speed > USB device using ehci_hcd and address 10 > Feb 7 10:05:43 kalau kernel: [ 918.012012] hub 2-1.1:1.0: USB hub found > Feb 7 10:05:43 kalau kernel: [ 918.012214] hub 2-1.1:1.0: 4 ports detected > Feb 7 10:05:44 kalau kernel: [ 918.287023] usb 2-1.1.4: new full > speed USB device using ehci_hcd and address 11 > Feb 7 10:05:44 kalau kernel: [ 918.384207] input: Keytouch as QWERTY > Panel as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1.4/2-1.1.4:1.0/input/input10 > Feb 7 10:05:44 kalau kernel: [ 918.384444] generic-usb > 0003:0926:3333.0004: input,hidraw1: USB HID v1.10 Keyboard [Keytouch > as QWERTY Panel] on usb-0000:00:1d.0-1.1.4/input0 That's the same as Message A above. > --unplugged message > Feb 7 10:06:23 kalau kernel: [ 957.281818] > drivers/hid/usbhid/hid-core.c: can't reset device, > 0000:00:1d.0-1.1.4/input0, status -71 > Feb 7 10:06:23 kalau kernel: [ 957.285901] usb 2-1.1: clear tt 1 > (00b0) error -71 > Feb 7 10:06:23 kalau kernel: [ 957.289920] > drivers/hid/usbhid/hid-core.c: can't reset device, > 0000:00:1d.0-1.1.4/input0, status -71 > Feb 7 10:06:23 kalau kernel: [ 957.293992] usb 2-1.1: clear tt 1 > (00b0) error -71 > Feb 7 10:06:23 kalau kernel: [ 957.298013] > drivers/hid/usbhid/hid-core.c: can't reset device, > 0000:00:1d.0-1.1.4/input0, status -71 > Feb 7 10:06:23 kalau kernel: [ 957.301979] usb 2-1.1: clear tt 1 > (00b0) error -71 > Feb 7 10:06:23 kalau kernel: [ 957.306015] > drivers/hid/usbhid/hid-core.c: can't reset device, > 0000:00:1d.0-1.1.4/input0, status -71 > Feb 7 10:06:23 kalau kernel: [ 957.309960] usb 2-1.1: clear tt 1 > (00b0) error -71 > Feb 7 10:06:23 kalau kernel: [ 957.314001] > drivers/hid/usbhid/hid-core.c: can't reset device, > 0000:00:1d.0-1.1.4/input0, status -71 > Feb 7 10:06:23 kalau kernel: [ 957.317947] usb 2-1.1: clear tt 1 > (00b0) error -71 > Feb 7 10:06:23 kalau kernel: [ 957.321973] > drivers/hid/usbhid/hid-core.c: can't reset device, > 0000:00:1d.0-1.1.4/input0, status -71 > Feb 7 10:06:23 kalau kernel: [ 957.325948] usb 2-1.1: clear tt 1 > (00b0) error -71 > Feb 7 10:06:23 kalau kernel: [ 957.332792] usb 2-1.1: USB > disconnect, address 10 > Feb 7 10:06:23 kalau kernel: [ 957.332798] usb 2-1.1.4: USB > disconnect, address 11 > Feb 7 10:06:23 kalau kernel: [ 957.333917] usb 2-1.1: clear tt 1 > (00b0) error -71 > Feb 7 10:06:23 kalau kernel: [ 957.334046] > drivers/hid/usbhid/hid-core.c: can't reset device, > 0000:00:1d.0-1.1.4/input0, status -71 Believe it or not, this is normal as well. > --plugged message (back to previous message error. Lets called it: Message B) > Feb 7 10:06:35 kalau kernel: [ 969.032120] usb 2-1.1: new high speed > USB device using ehci_hcd and address 12 > Feb 7 10:06:35 kalau kernel: [ 969.124550] hub 2-1.1:1.0: USB hub found > Feb 7 10:06:35 kalau kernel: [ 969.124715] hub 2-1.1:1.0: 4 ports detected > Feb 7 10:06:35 kalau kernel: [ 969.395186] usb 2-1.1.4: new full > speed USB device using ehci_hcd and address 13 > Feb 7 10:06:40 kalau kernel: [ 974.480087] generic-usb: probe of > 0003:0926:3333.0005 failed with error -32 This is clearly different from A, and it is not normal. > Everytime I plugged and unplugged keyboard it always produce "Message > A" and "Message B" randomly. It would help to see a usbmon trace for Message B. The trace you collected before appears to be for A. > But keyboard still not works. here is the full log. > http://pastebin.com/4yL13Be7 . Keyboard is on Bus 002 Device 009, here > is the grep result http://pastebin.com/hd8mPbPA The trace seems to show everything working correctly. It shows key presses and releases, just as one would expect. When you say the keyboard doesn't work, what do you mean? 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
