XFree shouldn't access hardware directly errors.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Version XFree86-4.4-0
I'm seeing a number of these kernel errors;

Feb 14 18:58:42 sidney kernel: atkbd.c: This is an XFree86 bug. It shouldn't 
access hardware directly.
Feb 14 19:00:58 sidney kernel: atkbd.c: Unknown key released (translated set 
2, code 0x7a on isa0060/serio0).
Feb 14 19:00:58 sidney kernel: atkbd.c: This is an XFree86 bug. It shouldn't 
access hardware directly.
Feb 14 19:00:58 sidney kernel: atkbd.c: Unknown key released (translated set 
2, code 0x7a on isa0060/serio0).
Feb 14 19:00:58 sidney kernel: atkbd.c: This is an XFree86 bug. It shouldn't 
access hardware directly.
Feb 14 23:15:50 sidney kernel: atkbd.c: Unknown key released (translated set 
2, code 0x7a on isa0060/serio0).
Feb 14 23:15:50 sidney kernel: atkbd.c: This is an XFree86 bug. It shouldn't 
access hardware directly.
Feb 15 07:56:32 sidney kernel: atkbd.c: Unknown key released (translated set 
2, code 0x7a on isa0060/serio0).
Feb 15 07:56:32 sidney kernel: atkbd.c: This is an XFree86 bug. It shouldn't 
access hardware directly.
Feb 15 07:56:32 sidney kernel: atkbd.c: Unknown key released (translated set 
2, code 0x7a on isa0060/serio0).
Feb 15 07:56:32 sidney kernel: atkbd.c: This is an XFree86 bug. It shouldn't 
access hardware directly.
-- 
Registered Linux user 193414
http://counter.li.org

"Trying"? My contribution was much closer to a "feeble wave in the general 
direction of something that might lead you one step closer to a solution 
if you squint really hard and do all of the work."
_______________________________________________
XFree86 mailing list
XFree86@xxxxxxxxxxx
http://XFree86.Org/mailman/listinfo/xfree86

[Index of Archives]     [X Forum]     [Xorg]     [XFree86 Newbie]     [IETF Announce]     [Security]     [Font Config]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux Kernel]

  Powered by Linux