no keyboard input since 48609

[luroh]

Not sure why but hrev48609 breaks all keyboard input in VMware and VirtualBox for me, pure gcc2.

[waddlesplash]

Is this a homegrown version, or are you using one of the prebuilt nightlies?

[bbjimmy]

Running on bare metal with a std gcc2h install, after updating to 48611 I got a similar issue. the keyboard does not reset whrn the desktop starts to show as it usually does. both the mouse and keyboaed are frozen. Even the Num-Lock and Caps-Lock keys are dead. no dafe-mode option will resolve it.

[luroh]

Replying to waddlesplash:

Is this a homegrown version, or are you using one of the prebuilt nightlies?

Home brewed but squeaky-clean gcc2 @release-vmware.

[luroh]

The problem is somewhat intermittent here. I just booted the same vmware image again and got keyboard back. It didn't survive "warm" reboot however and is now gone again.

[luroh]

serial log from vbox, hrev48613

[luroh]

Serial log attached from a "bad" boot, with kernel_debugger 'teams' -> 'threads' -> 'bt #IDs'. The mouse was working during this time, but not keyboard. Additional note: restarting input_server sometimes fixes the problem (...and sometimes hangs the mouse as well).

[anevilyak]

One thing that's of interest from that output: The PS/2 keyboard watcher thread that should be there is missing entirely.

[luroh]

serial log from a good boot, vbox, hrev48613

[anevilyak]

Further note, the bad boot doesn't have any indicator that the PS2 keyboard was found at all, while the good boot does, so it'd appear this might be a timing problem on the part of the PS2 driver. That one hasn't changed in nearly a month though, so it's somewhat odd that it'd suddenly start displaying issues.

[pulkomandy]

I get this problem on real hardware as well, for both keyboard and mouse.

[pulkomandy]

I had a further look at the logs and the sources. The keyboard device is published ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000 but then we never get the ps2: keyboard found from keyboard_open. However we also don't get the "keyboard probing failed" message from there.

I rebuilt the ps/2 driver with tracing enabled, and it seems keyboard_open isn't called at all. ps/2 interrupts from the keyboard result in syslog messages: "input/keyboard/at/0 not enabled, data 0xa6 dropped".

[taos]

Same problem on my laptop. Keyboard and touchpad (internal PS/2) still work on hrev48606 without problems, hrev48613 only accepts input by usb mouse/keyboard.

[pulkomandy]

Possibly fixed in hrev48617?

[luroh]

Sorry, still here in hrev48617.

[pulkomandy]

Fixed in hrev48619.

[AlienSoldier]

hrev48675

I still get intermitent boot without the keyboard (PS/2) on real hardware. I kill the input server and have it back.

When not working, the input server pathmonitor tread is very active.