Bug 254 - atkbd.c: unknown key released - XFree86 shouldn't access hardware directly
Summary: atkbd.c: unknown key released - XFree86 shouldn't access hardware directly
Status: CLOSED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: highest blocker
Assignee: Mike A. Harris
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-01 22:01 UTC by Mike A. Harris
Modified: 2011-09-27 10:20 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Mike A. Harris 2004-03-01 22:01:05 UTC
When running XFree86 under a recent 2.6.x kernel, many systems will have
the following error message logged from the kernel via syslog:

atkbd.c: unknown key released - XFree86 shouldn't access hardware directly

This is caused due to bad code in the XFree86 X server, in lnx_io.c (and
potentially lnx_kbd.c which contains largely duplicated source code).  The
same problem almost certainly exists in the xorg X server, so I'm logging the
bug here so it doesn't get lost.

I've written a patch which fixes this issue, and need to clean it up a bit
so it is ready for committing to the tree once I can confirm the problem
and fix work on the xorg server as well.

This is a placeholder defect report.
Comment 1 Mike A. Harris 2004-03-02 09:25:08 UTC
Link to the Red Hat bugzilla for this issue.

http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=atkbd
Comment 2 Egbert Eich 2004-03-04 11:55:02 UTC
So where is the fix?
Well... Never mind. I've fixed it anyway.
Comment 3 Mike A. Harris 2004-03-05 15:23:19 UTC
I never attached the fix, because:

>I've written a patch which fixes this issue, and need to clean it up a bit
>so it is ready for committing to the tree once I can confirm the problem
>and fix work on the xorg server as well.

Additionally, a new bug has been reported in which the ioctl seems to fail
still in lnx_kbd.c, which requires additional user testing before I commit
to the fix.  I filed this in bugzilla just so it would not get lost, however
I didn't plan on supplying a fix instantly, due to the above, so I assigned
it to myself.  Sorry for the confusion.
Comment 4 Jeremy Huddleston Sequoia 2011-09-27 10:20:34 UTC
Mass update: Close all bugs resolved over one year ago.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.