Re: kysmoops (was keysmoops)
mcclosk@cats.ucsc.edu wrote:
> Except that I didn't create /var/log/ksymoops (I wouldn't have known
> how to or why to; I had never heard of ksymoops before I noticed the
> existence of the log files); it must have been created automatically
> in the upgrade process from slink to frozen.
>
> But that seems wrong, given how hard and time-consuming it turned out
> to be to find out what the files were and what they are for; in the
> meantime, the directory just kept growing and growing with eight new
> files added each minute or so:
The directory is part of the modutils package, so it is created
automatically.
The weird thing is that you keep getting new files added every minute.
This implies modprobe or rmmod is running every minute. Compare to my
system, where I have the directory, and it gets just 6 files in it a day.
I suggest you look at /var/log/ksymoops/*.modules, and compare each
successive pair of files with diff.
joey@kite:/var/log/ksymoops>diff 20000527000455.modules 20000527010002.modules
0a1
> serial 18548 0 (autoclean) (unused)
joey@kite:/var/log/ksymoops>diff 20000527010002.modules 20000527011002.modules
1d0
< serial 18548 0 (autoclean) (unused)
My serial module is removed/installed a few times each day, because I
have cron jobs to turn my lights on and off, and it uses a serial
interface to control them.
You should be able to tell what module(s) are being removed and installed
every minute. Then try to track down what is making the modules get loaded.
It's probably some program trying to access them.
For example if you have a mixer running, and your sound card is not
initializing, I have noticed some mixer programs will try to access the
sound device several times a minute, causing the kernel to try to load
the sound drivers repeatedly.
--
see shy jo
Reply to: