system log grows quickly with USB evbug.c messages.
I'm running a standard debian binary kernel package (kernel-image-2.6.0-1-686)
and it seems that I get a message written to the system log for every USB
event. Since I have a USB mouse and keyboard, there are rather a lot of
events.
The messages looks like these (sorry for the wrapping):
Jan 27 10:58:58 localhost kernel: evbug.c: Event. Dev:
usb-0000:00:1f.2-2.2/input0, Type: 2, Code: 0, Value: -1
Jan 27 10:58:58 localhost kernel: evbug.c: Event. Dev:
usb-0000:00:1f.2-2.2/input0, Type: 0, Code: 0, Value: 0
Jan 27 10:58:58 localhost kernel: evbug.c: Event. Dev:
usb-0000:00:1f.2-2.1/input0, Type: 1, Code: 103, Value: 1
Jan 27 10:58:58 localhost kernel: evbug.c: Event. Dev:
usb-0000:00:1f.2-2.1/input0, Type: 0, Code: 0, Value: 0
Jan 27 10:58:58 localhost kernel: evbug.c: Event. Dev:
usb-0000:00:1f.2-2.1/input0, Type: 1, Code: 103, Value: 0
Jan 27 10:58:58 localhost kernel: evbug.c: Event. Dev:
usb-0000:00:1f.2-2.1/input0, Type: 0, Code: 0, Value: 0
Jan 27 10:58:59 localhost kernel: evbug.c: Event. Dev:
usb-0000:00:1f.2-2.2/input0, Type: 2, Code: 1, Value: 1
Jan 27 10:58:59 localhost kernel: evbug.c: Event. Dev:
usb-0000:00:1f.2-2.2/input0, Type: 0, Code: 0, Value: 0
Jan 27 10:58:59 localhost kernel: evbug.c: Event. Dev:
usb-0000:00:1f.2-2.1/input0, Type: 1, Code: 28, Value: 1
Jan 27 10:58:59 localhost kernel: evbug.c: Event. Dev:
usb-0000:00:1f.2-2.1/input0, Type: 0, Code: 0, Value: 0
Is this just my problem, or is everyone having it? No one else seems to be
complaining about it. I noticed this problem because the partition
with /var/log on it has only about 190M free, which gets eaten through after
a few hours.
If it matters, I use grub.
-d
Reply to: