summaryrefslogtreecommitdiffstats
path: root/usr.bin/ssh
diff options
context:
space:
mode:
authorcsapuntz <csapuntz@openbsd.org>2000-12-19 06:58:39 +0000
committercsapuntz <csapuntz@openbsd.org>2000-12-19 06:58:39 +0000
commit8fa2bf4de8faa3ff9981c1a1dbb73ae46ca5e1a3 (patch)
treeb4df10ab25d925ab0017dc1740a924b45ed52c2b /usr.bin/ssh
parentA DMA transfer of 4 bytes was failing to complete correctly (diff)
downloadwireguard-openbsd-8fa2bf4de8faa3ff9981c1a1dbb73ae46ca5e1a3.tar.xz
wireguard-openbsd-8fa2bf4de8faa3ff9981c1a1dbb73ae46ca5e1a3.zip
This fixes keyboard lock-ups I was getting wiggling the mouse in
console mode while using my omnicube KVM switch. The keyboard lock-ups were caused by the keyboard/mouse interface controller's input buffer filling up. This was caused because the mouse was sending data to the computer and the pms driver wasn't draining it. The driver used to rely on the fact that it could disable the mouse device when the mouse driver was closed. Disabling the mouse device prevents it from sending data to the computer. At the same time pms disabled the mouse device, pms disabled interrupt notification of the arrival of new data. This regime doesn't work so well with KVM switches which re-enable the mouse. In this case, the mouse will send data to the computer but the keyboard/moust interface controller won't raise an interrupt (because pms disabled interrupts). pms will never read from the input buffer.
Diffstat (limited to 'usr.bin/ssh')
0 files changed, 0 insertions, 0 deletions