[lkml]   [2005]   [Oct]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] Disable the most annoying printk in the kernel
On Fri, Oct 28, 2005 at 10:51:32PM +0200, Pavel Machek wrote:
> Well, keyboard detected and reported an error. Kernel reacted with
> printk(). You are removing that printk(). I can understand that,
> printk is really annoying, but I really believe _some_ error handling
> should be added there if you remove the printk.

What do you suggest?

Having a TP 380XD which regularly produces this annoying message,
it's just logspam. There's no noticable failure.

Plus, kernels previous to ones with the new input subsystem just
used to ignore the scancode (from v2.[24].xx):

int pckbd_translate(unsigned char scancode, unsigned char *keycode,
char raw_mode)
/* 0xFF is sent by a few keyboards, ignore it. 0x00 is error */
if (scancode == 0x00 || scancode == 0xff) {
prev_scancode = 0;
return 0;

Russell King
Linux kernel 2.6 ARM Linux -
maintainer of: 2.6 Serial core
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-10-28 23:02    [W:0.067 / U:4.924 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site