Bug 234735
Summary: | [mmconf] USB keyboard keystrokes are missed or repeated on virtual terminals | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jacob Thompson <jakethompson1> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | triage |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | bzcl34nup | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-07 01:23:58 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
Jacob Thompson
2007-04-01 03:13:51 UTC
This does not sound like a kernel issue to me. Most likely, either X or something else is keeping /dev/kbd open, or something similar is happening. There was some strangenness recently due to switch of X configuration tools to evdev. Please try to log over the network while the symptom is present and poke around with lsof. I logged into the machine over a null modem cable while running X and at the console, there is no device containing "kbd" open and in fact, there is no such file /dev/kbd. The issue also goes away when using a PS/2 keyboard. I also tried rebooting with init=/bin/cat on the kernel command line so that no daemons would be running trying to access the keyboard. With just cat running, the problem is even worse, I get tteeeeeeeesssssssstttttttt. Since this is a 64-bit machine, I tried booting the x86_64 kernel from a USB key. The problem is still there. It occurs with the kernel on Fedora 7 test 3 LiveCD, the Fedora 7 test 3 bootdisk.img for both i386 and x86_64, as well as on the original Fedora Core 6 install CD (2.6.18?). On this machine, I have to boot with acpi=off, reported in bug 234733. Could this be related? Bulk message: Fedora 7 test bugs should be filed against "devel", not against test1/2/3. This isn't obvious, I know. Moving this report so it isn't lost. This problem is not happening anymore with current kernels using the boot option with the option pci=nommconf. Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. This bug has been in NEEDINFO for more than 30 days since feedback was first requested. As a result we are closing it. If you can reproduce this bug in the future against a maintained Fedora version please feel free to reopen it against that version. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp |