Opened 8 years ago

Closed 7 weeks ago

#7897 closed bug (invalid)

USB Keyboard no longer working

Reported by: tqh Owned by: mmlr
Priority: normal Milestone: R1
Component: Drivers/USB/OHCI Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

Some time in the latest year the usb-keyboard on one of my computers stopped working. Tested with hrev42569.

Removing and inserting it in Haiku (with debug in usb-hid) gives:

KERN: usb hub 2: port 1: device removed
KERN: usb hub 2: KERN: port 1 disabled
KERN: usb_hid: publish_devices()
KERN: usb_hid: publishing input/mouse/usb/0
KERN: usb_hid: publishing input/keyboard/usb/0
KERN: usb_hid: find_device(input/mouse/usb/0)
KERN: usb_hid: find_device(input/keyboard/usb/0)
KERN: usb hub 27: port 1: new device connected
KERN: usb ehci -1: lowspeed device connected, giving up port ownership
KERN: usb hub 2: port 1: new device connected
KERN: usb error control pipe 31: timeout waiting for queued request to complete
Last message repeated 2 times
KERN: usb error ohci -1: error while setting device address
KERN: usb error control pipe 31: timeout waiting for queued request to complete
Last message repeated 1 time
KERN: usb_hid: waiting for report returned with result: No error
KERN: usb_hid: got mouse report
KERN: usb_hid: control(0x830e2638, 10099, 0x78137ef0, 40)
KERN: usb_hid: scheduling interrupt transfer of 8 bytes
KERN: usb_hid: waiting for report returned with result: No error
KERN: usb_hid: got mouse report

Syslog and linux lsusb -vv is attached. Only mouse and keyboard attached on USB, mouse works fine.

Attachments (2)

syslog.txt (85.2 KB ) - added by tqh 8 years ago.
lsusb-vv.linux.txt (17.5 KB ) - added by tqh 8 years ago.

Download all attachments as: .zip

Change History (10)

by tqh, 8 years ago

Attachment: syslog.txt added

by tqh, 8 years ago

Attachment: lsusb-vv.linux.txt added

comment:1 by korli, 8 years ago

Component: Add-Ons/Input MethodsDrivers/USB
Owner: changed from korli to mmlr

comment:2 by Disreali, 8 years ago

How were you able to remove and the insert the keyboard if it was not working?

I ask because I just installed hrev43192-2h nightly and the keyboard stopped working after a couple minutes. The media-addon-server crashed and as soon as I clicked the debug button in the resulting error box, the keyboard ceased to respond to input.

in reply to:  2 ; comment:3 by mmlr, 8 years ago

Replying to Disreali:

How were you able to remove and the insert the keyboard if it was not working?

I think he meant physically removing (disconnecting) and re-inserting the keyboard from USB.

I ask because I just installed hrev43192-2h nightly and the keyboard stopped working after a couple minutes. The media-addon-server crashed and as soon as I clicked the debug button in the resulting error box, the keyboard ceased to respond to input.

This bug report is a bit curious as the initial suspect of an interrupt issue kind of doesn't fit since the mouse still works. A keyboard stopping sounds different enough to warrant a new bug report though. Initially I'd suspect some interrupt storm taking away the (lower priority) USB interrupts, a transfer leak in some USB driver causing USB memory exhaustion or something input_server related that quits the input device. In either case, please open a bug report and attach as much info as you can (a syslog and maybe a listusb -v would be nice).

in reply to:  3 comment:4 by Disreali, 8 years ago

Replying to mmlr:

I think he meant physically removing (disconnecting) and re-inserting the keyboard from USB.

DOH!! Really showing my age here. I still have it ingrained in my mind to never unplug a keyboard while the system is on.

I ask because I just installed hrev43192-2h nightly and the keyboard stopped working after a couple minutes. The media-addon-server crashed and as soon as I clicked the debug button in the resulting error box, the keyboard ceased to respond to input.

This bug report is a bit curious as the initial suspect of an interrupt issue kind of doesn't fit since the mouse still works. A keyboard stopping sounds different enough to warrant a new bug report though. Initially I'd suspect some interrupt storm taking away the (lower priority) USB interrupts, a transfer leak in some USB driver causing USB memory exhaustion or something input_server related that quits the input device. In either case, please open a bug report and attach as much info as you can (a syslog and maybe a listusb -v would be nice).

I have already submitted ticket:8077, which may have the same cause as I describe above. I will attach a listusb to that ticket.

comment:5 by x-ist, 7 years ago

Is it possible that you plug-in a PS/2 keyboard in addition to your USB keyboard and then repeat your test? According to your syslog the ps2 driver has issues too and the ps2 keyboard wouldn't work as well. That would indicate that #8987 is a related issue.

comment:6 by waddlesplash, 5 years ago

Component: Drivers/USBDrivers/USB/OHCI

Filtering OHCI tickets from Drivers/USB to Drivers/USB/OHCI.

comment:7 by cocobean, 18 months ago

hrev52017 reviewed. Two things I've done is either set 'USB Legacy' in the BIOS or use a USB-to-PS/2 adapter to use the PS/2 port for a mouse and/or keyboard. There are various things that happen with USB-mice/keyboard configurations not specific to Haiku (usually when booting->desktop initialization occurs in the initialization handling/interrupts both a USB-mice/keyboard combination. Try to see if a BIOS/firmware update can fix the issue and retest on a recent nightly image (suggest hrev52017 or higher).

We can close this ticket and consolidate for driver enhancement.

Last edited 18 months ago by cocobean (previous) (diff)

comment:8 by tqh, 7 weeks ago

Resolution: invalid
Status: newclosed

Found that I reported this eons ago. Closing as Haiku has improved a lot since then.

Note: See TracTickets for help on using tickets.