Bug 58344
Summary: | Keyboard locks up | ||
---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Sammy <umar> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1.0 | CC: | mharris |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-01-23 14:41:19 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sammy
2002-01-14 18:57:30 UTC
The only thing I can think of that might cause such a problem is a misconfigured PS/2 mouse, while using a PS/2 keyboard. This can mess up the keyboard controller as well. Dunno if that is relevant or not, just a data point. Well, there was a thread on this in one of the redhat news groups. The problem is with the 2.4.9-13 kernel....and switching to 2.4.17 kernel SOLVES the problem. I just tested it. FYI OK, assigning to kernel. Keyboard lockups are still happening with latest rawhide. People in the news group claim running the stock kernel 2.4.17 solved their problem. Here is EXACTLY what happens and why it wan't happen to everybody: If you are using an external modem via mgetty or uugetty (say port ttyS0). Every time mgetty is respawned (call comes in) keyboard locks up. If you physically kill mgetty or uugetty (kill -9 PidOfMgetty) the keyboard lock instantly. Since the same thing is happening with both mgetty and getty_ps packages (compiled on rawhide) this seems like some problem with inittab unless it is some kind of a lock problem. Somehow the keyboard grabbing is competing with X and locking the keyboard. I hope we can find a solution since this is pretty annoying. SOLVED!!! Finally I tracked it down to SysVinit-2.79-x. I upgraded sysvinit to 2.84 and all is welll now. None of the things above cause this race condition. I am closing this and will report to packager of SysVinit as a new bug. |