Summary: | USB keyboard and mouse connected to a KVM doesn't detect immediately. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Anand <n00b.gentoouser> |
Component: | [OLD] Server | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | n00b.gentoouser, xmw |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | .config file attachment |
Description
Anand
2010-05-17 15:31:03 UTC
Hello Anand, did this occur after an kernel update? Do you have any old kernel before that happend? If I understand you right, but my knowledge is limited to old i8042 KVM, the OS should always see an attached device w/o disconnect reconnect. Is that right? Can you clear up the log buffer with `dmesg -c` and do some actions like switch the KVM away from Gentoo box and reconnet back some 10 seconds later and investigate/poste the newly generated dmesg output, please? Do you use any Xorg on this machine? Is this problem limited to console? If you've an Xorg server running the /var/log/Xorg.0.log from the above `cycle` might be usefull, too. Sorry, but I dont have a glue atm. Michael Hi Michael, 1) No, this did not happen after a kernel update. This happened after I had to wipe out my drive and do a fresh install. It used to work prior to the clean install. The reason for the clean install is totally unrelated. The same issue is noticed on all the kernels I listed in my first post. 2) Yes, the expected result is that the keyboard & mouse attached to the (USB) KVM switch will be detected like any other hot-pluggable/swappable USB device. 3) Cleared dmesg per your suggestion. The dmesg output after waiting for 10-20 seconds and reconnecting the KVM is below. 4) I run Xorg version 1.7.6. But I doubt running Xorg has much to do with this. Perhaps I am not understanding your reason to inquire about Xorg but I imagine keyboards and mice attached via USB work regardless. At least in my experience they have. In any case, I am also listing the last 50 lines of the Xorg.0.log - the whole file is over 700 lines. In addition to the KVM switch a Dell keyboard and mouse is connected directly to the box. Let me know if you need any other info. Thanks, Anand tail -n 50 /var/log/Xorg.0.log output: (II) NV(0): EDID (in hex): (II) NV(0): 00ffffffffffff0010ac17a0534b3131 (II) NV(0): 0e11010380342178eeee91a3544c9926 (II) NV(0): 0f5054a54b008180a940714fb3000101 (II) NV(0): 010101010101283c80a070b023403020 (II) NV(0): 360007442100001a000000ff00434333 (II) NV(0): 303237343231314b5320000000fc0044 (II) NV(0): 454c4c20323430375746500a000000fd (II) NV(0): 00384c1e5311000a20202020202000f4 (II) NV(0): EDID vendor "DEL", prod id 40983 (II) NV(0): Using hsync ranges from config file (II) NV(0): Using vrefresh ranges from config file (II) NV(0): Printing DDC gathered Modelines: (II) NV(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz) (II) NV(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (II) NV(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz) (II) NV(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (II) NV(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz) (II) NV(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz) (II) NV(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz) (II) NV(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (II) NV(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz) (II) NV(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz) (II) NV(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz) (II) NV(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz) (II) NV(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz) (II) NV(0): EDID vendor "DEL", prod id 40983 (II) config/hal: Adding input device Dell Dell USB Keyboard (**) Dell Dell USB Keyboard: always reports core events (**) Dell Dell USB Keyboard: Device: "/dev/input/event3" (II) Dell Dell USB Keyboard: Found keys (II) Dell Dell USB Keyboard: Configuring as keyboard (II) XINPUT: Adding extended input device "Dell Dell USB Keyboard" (type: KEYBOARD) (**) Option "xkb_rules" "evdev" (**) Option "xkb_model" "evdev" (**) Option "xkb_layout" "us" (II) config/hal: Adding input device HID 04b3:310b (**) HID 04b3:310b: always reports core events (**) HID 04b3:310b: Device: "/dev/input/event4" (II) HID 04b3:310b: Found 3 mouse buttons (II) HID 04b3:310b: Found scroll wheel(s) (II) HID 04b3:310b: Found relative axes (II) HID 04b3:310b: Found x and y relative axes (II) HID 04b3:310b: Configuring as mouse (**) HID 04b3:310b: YAxisMapping: buttons 4 and 5 (**) HID 04b3:310b: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device "HID 04b3:310b" (type: MOUSE) (**) HID 04b3:310b: (accel) keeping acceleration scheme 1 (**) HID 04b3:310b: (accel) acceleration profile 0 (II) HID 04b3:310b: initialized for relative axes. dmesg output: [2136551.164687] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136551.165209] hub 2-1:1.0: port 1, status 0101, change 0001, 12 Mb/s [2136552.721157] hub 2-1:1.0: debounce: port 1: total 1500ms stable 0ms status 0x101 [2136552.721163] hub 2-1:1.0: connect-debounce failed, port 1 disabled [2136552.721168] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136552.721663] hub 2-1:1.0: port 1, status 0101, change 0001, 12 Mb/s [2136554.277731] hub 2-1:1.0: debounce: port 1: total 1500ms stable 0ms status 0x101 [2136554.277736] hub 2-1:1.0: connect-debounce failed, port 1 disabled [2136554.277742] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136554.483502] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136554.484037] hub 2-1:1.0: port 1, status 0101, change 0001, 12 Mb/s [2136556.039848] hub 2-1:1.0: debounce: port 1: total 1500ms stable 0ms status 0x101 [2136556.039853] hub 2-1:1.0: connect-debounce failed, port 1 disabled [2136556.039858] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136556.270555] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136556.270965] hub 2-1:1.0: port 1, status 0101, change 0001, 12 Mb/s [2136557.826912] hub 2-1:1.0: debounce: port 1: total 1500ms stable 0ms status 0x101 [2136557.826917] hub 2-1:1.0: connect-debounce failed, port 1 disabled [2136557.826922] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136558.057608] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136558.057986] hub 2-1:1.0: port 1, status 0101, change 0001, 12 Mb/s [2136559.613968] hub 2-1:1.0: debounce: port 1: total 1500ms stable 0ms status 0x101 [2136559.613973] hub 2-1:1.0: connect-debounce failed, port 1 disabled [2136559.613979] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136559.844680] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136559.845197] hub 2-1:1.0: port 1, status 0101, change 0001, 12 Mb/s [2136561.401899] hub 2-1:1.0: debounce: port 1: total 1500ms stable 0ms status 0x101 [2136561.401905] hub 2-1:1.0: connect-debounce failed, port 1 disabled [2136561.401910] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136561.631719] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136561.632256] hub 2-1:1.0: port 1, status 0101, change 0001, 12 Mb/s [2136563.188954] hub 2-1:1.0: debounce: port 1: total 1500ms stable 0ms status 0x101 [2136563.188959] hub 2-1:1.0: connect-debounce failed, port 1 disabled [2136563.188965] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136563.418774] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136563.419310] hub 2-1:1.0: port 1, status 0101, change 0001, 12 Mb/s [2136564.976001] hub 2-1:1.0: debounce: port 1: total 1500ms stable 0ms status 0x101 [2136564.976007] hub 2-1:1.0: connect-debounce failed, port 1 disabled [2136564.976012] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136565.205828] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136565.206364] hub 2-1:1.0: port 1, status 0101, change 0001, 12 Mb/s [2136566.763032] hub 2-1:1.0: debounce: port 1: total 1500ms stable 0ms status 0x101 [2136566.763037] hub 2-1:1.0: connect-debounce failed, port 1 disabled [2136566.763042] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136566.992802] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136566.993286] hub 2-1:1.0: port 1, status 0101, change 0001, 12 Mb/s [2136568.548990] hub 2-1:1.0: debounce: port 1: total 1500ms stable 0ms status 0x101 [2136568.548995] hub 2-1:1.0: connect-debounce failed, port 1 disabled [2136568.549001] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136568.779856] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136568.780345] hub 2-1:1.0: port 1, status 0101, change 0001, 12 Mb/s [2136570.337045] hub 2-1:1.0: debounce: port 1: total 1500ms stable 0ms status 0x101 [2136570.337051] hub 2-1:1.0: connect-debounce failed, port 1 disabled [2136570.337056] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136570.566992] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136570.567528] hub 2-1:1.0: port 1, status 0101, change 0001, 12 Mb/s [2136572.124088] hub 2-1:1.0: debounce: port 1: total 1500ms stable 0ms status 0x101 [2136572.124094] hub 2-1:1.0: connect-debounce failed, port 1 disabled [2136572.124099] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136572.354047] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0002 [2136572.354582] hub 2-1:1.0: port 1, status 0101, change 0001, 12 Mb/s @kernel: Do you have any idea? Are there multiple usb ports on the Gentoo box you can try? You might have tried this already (In reply to comment #4) > Are there multiple usb ports on the Gentoo box you can try? You might have > tried this already > Yes, I've tried this on different USB ports and it still doesn't seem to fix the problem. Can you post your .config? Is ehci_hcd enabled in your kernel? If it's configured as a module, can you unload it and then test? (In reply to comment #6) > Can you post your .config? > > Is ehci_hcd enabled in your kernel? If it's configured as a module, can you > unload it and then test? > .config attached. No ehci_hcd is not enabled AFAIK. Created attachment 251121 [details]
.config file attachment
(In reply to comment #7) > (In reply to comment #6) > > Can you post your .config? > > > > Is ehci_hcd enabled in your kernel? If it's configured as a module, can you > > unload it and then test? > > > > .config attached. No ehci_hcd is not enabled AFAIK. > I do apologize, I seem to have forgotten the attachment. I'm attaching it now. (In reply to comment #9) > > > Is ehci_hcd enabled in your kernel? If it's configured as a module, can you > > > unload it and then test? > > > > > > > .config attached. No ehci_hcd is not enabled AFAIK. ehci_hcd is configured as a module: CONFIG_USB_EHCI_HCD=m Can you unload it and then test? Can you also test with the latest gentoo-sources which is gentoo-sources-2.6.36-r5 as of this moment. Feel free to reopen with the results from comment #10 |