On Fri, Feb 09, 2007 at 11:51:18AM -0800, tom arnall wrote: > On Friday 09 February 2007 11:44, Andrew Sackville-West wrote: > > On Fri, Feb 09, 2007 at 10:36:46AM -0800, tom arnall wrote: > > > On Wednesday 07 February 2007 11:43, Andrew Sackville-West wrote: > > > > On Wed, Feb 07, 2007 at 11:32:43AM -0800, tom arnall wrote: > > > > > last night my system ground to a halt with a full disk. looking at > > > > > the logs, i discovered that they were the main if not the only > > > > > resource hogs. (haven't looked for other sources of spurious disk > > > > > usage). below is a sample of 'debug'. 'kern.log' and 'syslog' have > > > > > the same messages. you can tell by the time stamps that something is > > > > > going wild in my system. > > > > > > > > > > > > > > > > > > > > Feb 7 10:50:26 localhost kernel: evbug.c: Event. Dev: > > > > > isa0060/serio0/input0, Type: 4, Code: 4, Value: 31 > > > > > > > > my understanding is that evbug is strictly for debugging (hence the > > > > big output). Unless you are specifically using it you should rmmod it > > > > and blacklist it or remove it from your kernel altogether. > > > > > > > > interestingly, I don't find it in my modules anywhere (sid here) but I > > > > seem to recall it in earlier kernels. I wonder if you are stuck in a > > > > transition -- some upgrade has removed it from your blacklists, but > > > > its still in the kernel and getting inserted automatically. > > > > > > getting rid of evbug does it, but haven't been able to blacklist the > > > thing. my modprobe.d/blacklist says: > > > > > > # evbug is a debug tool and should be loaded explicitly > > > blacklist evbug > > > > > > but it's still firing at bootup. > > > > rename the file might work. > > > > > dont' feel easy jerry-rigging my way out of the problem. do you have any ideas > for why the modprobe.d/blacklist method is not working? I agree. can you tell who is inserting the module? maybe its udev/hotplug somehow. put it in /etc/hotplug/blacklist.d/ as well? but that doesn't make sense to me. mine is listed in modprobe.d/blacklist (yep, I found it, forgot to escape my globbing in find...bleh.) and works fine. what kernel? I've seen other posts about blacklisting not working and specifically about it generating an error in the boot logs, so you might check that.. A
Attachment:
signature.asc
Description: Digital signature