evbug causes strange dmesg output

Bug #60716 reported by dorpm on 2006-09-16
2
Affects Status Importance Assigned to Milestone
module-init-tools (Ubuntu)
Undecided
Unassigned

Bug Description

When the module evbug is loaded at startup the output of dmesg contains only messages like these:

evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 31
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 31, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 34
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 34, Value: 1
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 34
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 34, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 28
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 28, Value: 1
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 28
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 28, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0

I have blacklisted the module now and have again a dmesg with more content.

What is this module for? Does it make sense to deactivate it? So far I haven´t recognized any impacts on my system.

Florian

dorpm (dorpmueller) on 2006-09-16
description: updated
Kai Kasurinen (kai-kasurinen) wrote :

evbug is Input driver event debug module.

It should not be autoloaded. It is listed in /etc/modprobe.d/blacklist (or
should be). If it isn't on your system, then perhaps you modifed that file at
some point.

Does the file /etc/modprobe.conf exist? It should not exist. (On an modern system that file OVERRIDES all distribution-supplied configuration, including blacklists, rather than augments it.)

see bug 27984 for more info.

dorpm (dorpmueller) wrote :

I´ve put it manually into /etc/modprobe.d/blacklist. It was not there by default.

Florian

This module has always been blacklisted, if it wasn't for you, you modified the modprobe blacklist

Changed in module-init-tools:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers