Re: Logging goes beserk

[Derek Broughton <derek@pointerstop.ca>]

On Tuesday 17 May 2005 14:44, Christian Birkholm Clausen wrote:
> Hey guys,
>
> So, 2.6.11.9 working good on my IBM T42. One small thing though; syslog,
> kern.log and debug are growing rapidly. Upto 117mb since yesterday pr.
> file approximately... :( Seem to get filled with alot of usb and isa
> logging. 10-15 pr. second. I turned off every debugging feature I could
> find in the kernel and recompiled. But it hasn't helped. Can't find any
> bad settings in syslog.cong, but then again I'm not sure that that's the
> right place to look. Guess it's a kernel-thing..
>
> Examples from syslog:
>
> May 16 20:40:31 localhost kernel: evbug.c: Event. Dev:
> usb-0000:00:1d.1-2/input0, Type: 4, Code: 4, Value: 65585
> May 16 20:40:31 localhost kernel: evbug.c: Event. Dev:
> usb-0000:00:1d.1-2/input0, Type: 2, Code: 1, Value: 1
> May 16 20:40:31 localhost kernel: evbug.c: Event. Dev:
> usb-0000:00:1d.1-2/input0, Type: 0, Code: 0, Value: 0
>
> May 16 20:40:55 localhost kernel: evbug.c: Event. Dev:
> isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
> May 16 20:40:55 localhost kernel: evbug.c: Event. Dev:
> isa0060/serio1/input0, Type: 3, Code: 28, Value: 4
> May 16 20:40:55 localhost kernel: evbug.c: Event. Dev:
> isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
>
> Any ideas?
>
evbug has always been blacklisted by default in any debian version I've used.  
It's in /etc/hotplug/blacklist and _shouldn't_ be in /etc/modules.  Of 
course, there are all sorts of places a module can get loaded.
-- 
derek