linux-kernel - Re: keyboard.c: Stop flooding dmesg with useless warnings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 25 Mar 2007 11:16:04 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Parag Warudkar <parag.warudkar@...il.com>
Cc:	Dmitry Torokhov <dtor@...ightbb.com>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: keyboard.c: Stop flooding dmesg with useless warnings

On Sun, 25 Mar 2007, Parag Warudkar wrote:

> > > Yes this is a USB keyboard. Any hint as to where I should start 
> > > looking to make the driver not emit input event for keycode==0?
> > Was it always doing that? I'll add Jiri Kosina to the CC list as he's 
> > involved with HID now.
> Something (some keypress?) triggers it (by default it doesn't happen 
> immediately after a boot) - but once it starts it doesn't seem to stop 
> printing.

First, is there any specific kernel version where this started to happen 
to you, or is this long-standing bug you have been experiencing with older 
kernels too?

It would be useful if you could compile your kernel with CONFIG_HID_DEBUG 
and send the output both from the time the keyboard is connected and also 
when things go wild.

-- 
Jiri Kosina
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/