Bug 4596 - Keyboard lockup after a few seconds when serial console enabled
Summary: Keyboard lockup after a few seconds when serial console enabled
Status: REJECTED UNREPRODUCIBLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: Dmitry Torokhov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-07 08:45 UTC by Robin Green
Modified: 2008-03-05 05:42 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.12-rc3
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Robin Green 2005-05-07 08:45:38 UTC
Distribution: Fedora Core development (pre-FC4)
Hardware Environment: PC, 32-bit Athlon, PS/2 keyboard
Software Environment: KDM login manager
Problem Description: 

I have a serial console attached on /dev/ttyS0 (it is another Linux machine).
The serial console seems to work; however, if I boot up with the serial console
enabled, a few seconds after starting to log in at the kdm login manager, the
keyboard locks up, consistently every time. It is completely inoperable - I
cannot switch to a virtual console with CTRL+ALT+F1, and the Num Lock key does
not cause the Num Lock LED to light up. However, my PS/2 mouse still works fine.

Steps to reproduce:
Boot with the following grub command line
kernel /vmlinuz-2.6.12-rc3 ro root=/dev/VolGroup00/LogVol00 noacpi elevator=cfq
console=tty1 console=ttyS0,38400
Comment 1 Robin Green 2005-05-08 04:43:44 UTC
If I instead boot into runlevel 3, the keyboard is fine until I do "init 5", at
which point the problem reoccurs.

If I go down to runlevel 3 from runlevel 5 (by typing "init 3" at the serial
console) the keyboard is still locked up - even ctrl+alt+del does not work.
(NOTE: I cannot see any virtual terminals because of an X.org virtual terminal
restore corruption bug - but virtual terminal _input_ usually works after X has
corruptly restored a virtual terminal: it's just the output that's corrupted.
Therefore I believe the continuing keyboard lockup here is due to this bug, not
due to the X.org bug.)

I managed to workaround this bug one time by randomly banging on the keyboard
:-) - but this workaround is not reproducable.
Comment 2 Natalie Protasevich 2007-11-18 00:15:47 UTC
Robin,
Does it work better with recent kernel/Xorg?
Thanks.
Comment 3 Natalie Protasevich 2008-03-05 05:42:59 UTC
Closing the bug. Please reopen if confirmed with latest kernel.

Note You need to log in before you can comment on or make changes to this bug.