Bug 86584 – kernel: pc_keyb: controller jammed (0x1F)

Bug 86584 - kernel: pc_keyb: controller jammed (0x1F)

Summary:	kernel: pc_keyb: controller jammed (0x1F)

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	kernel (Show other bugs)
Sub Component:
Version:	8.0
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Arjan van de Ven
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	86570 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-03-25 17:22 EST by Tim Keitt
Modified:	2007-04-18 12:52 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-06-22 12:44:47 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Last boot log (for hardware info) (6.93 KB, text/plain) 2003-03-25 17:24 EST, Tim Keitt	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Tim Keitt 2003-03-25 17:22:09 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
I've been getting "pc_keyb: controller jammed" messages in my logs. These are
associated with the keyboard locking up. Things work fine after restarting X.
These _seem_ to occur when the machine is under load. I've run extensive
hardware diagnostics on the machine and haven't found anything.

Version-Release number of selected component (if applicable):
2.4.18-27.8.0smp

How reproducible:
Sometimes

Steps to Reproduce:
1. wait awhile...
2. run heavy load???
3.
    

Additional info:

Comment 1 Tim Keitt 2003-03-25 17:24:15 EST

Created attachment 90717 [details]
Last boot log (for hardware info)

Comment 2 Tim Keitt 2003-03-25 17:26:59 EST

*** Bug 86570 has been marked as a duplicate of this bug. ***

Comment 3 Tim Keitt 2003-03-26 19:10:12 EST

Still seeing this, and its deinitely happenning when cpu's are running high
loads. Is this the too-short-mdelay bug discussed on the kernel lists? Some
messages the system log:

Mar 25 10:17:51 keittlab kernel: pc_keyb: controller jammed (0x1D).
Mar 25 14:06:46 keittlab kernel: pc_keyb: controller jammed (0x1F).
Mar 25 17:41:25 keittlab kernel: pc_keyb: controller jammed (0x17).
Mar 26 17:59:43 keittlab kernel: pc_keyb: controller jammed (0x17).
Mar 26 17:59:45 keittlab kernel: pc_keyb: controller jammed (0x1F).
Mar 26 18:00:04 keittlab kernel: pc_keyb: controller jammed (0x17).

Mar 24 18:11:54 keittlab gnome-name-server[28047]: input condition is: 0x11, exiting
Mar 25 10:29:26 keittlab gnome-name-server[3033]: input condition is: 0x11, exiting
Mar 25 13:03:37 keittlab gnome-name-server[1310]: input condition is: 0x11, exiting
Mar 25 14:07:46 keittlab gnome-name-server[4620]: input condition is: 0x11, exiting
Mar 25 18:17:43 keittlab gnome-name-server[7640]: input condition is: 0x11, exiting
Mar 26 14:05:43 keittlab gnome-name-server[26914]: input condition is: 0x11, exiting
Mar 26 14:13:46 keittlab gnome-name-server[29939]: input condition is: 0x11, exiting
Mar 26 17:59:55 keittlab gnome-name-server[31365]: input condition is: 0x11, exiting

Comment 4 Tim Keitt 2003-06-22 12:44:47 EDT

This _was_ the mdelay kernel bug (it was fixed -- silently -- in the RH 9 kernel
source).

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