Modules: errors in logs

LadFromWales85 · 07-25-2004, 05:52 PM

Just been looking through my system logs, and find lots of errors loading certain modules.

Code:

Jul 25 03:06:43 shaunsputer insmod: /lib/modules/2.4.26/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Jul 25 03:06:43 shaunsputer insmod: /lib/modules/2.4.26/kernel/drivers/cdrom/cdu31a.o.gz: init_module: Input/output error
Jul 25 03:06:43 shaunsputer insmod: /lib/modules/2.4.26/kernel/drivers/cdrom/cdu31a.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
Jul 25 03:06:43 shaunsputer insmod: /lib/modules/2.4.26/kernel/drivers/cdrom/cdu31a.o.gz: insmod block-major-15 failed
Jul 25 03:06:49 shaunsputer insmod: /lib/modules/2.4.26/kernel/drivers/cdrom/mcd.o.gz: init_module: Input/output error
Jul 25 03:06:49 shaunsputer insmod: /lib/modules/2.4.26/kernel/drivers/cdrom/mcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
Jul 25 03:06:49 shaunsputer insmod: /lib/modules/2.4.26/kernel/drivers/cdrom/mcd.o.gz: insmod block-major-23 failed
Jul 25 03:07:00 shaunsputer kernel: Trying to free nonexistent resource <00000340-00000343>
Jul 25 03:07:00 shaunsputer insmod: /lib/modules/2.4.26/kernel/drivers/cdrom/sjcd.o.gz: init_module: Input/output error
Jul 25 03:07:00 shaunsputer insmod: /lib/modules/2.4.26/kernel/drivers/cdrom/sjcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
Jul 25 03:07:00 shaunsputer insmod: /lib/modules/2.4.26/kernel/drivers/cdrom/sjcd.o.gz: insmod block-major-18 failed
Jul 25 03:07:00 shaunsputer insmod: /lib/modules/2.4.26/kernel/drivers/cdrom/cm206.o.gz: init_module: Input/output error
Jul 25 03:07:00 shaunsputer insmod: /lib/modules/2.4.26/kernel/drivers/cdrom/cm206.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
Jul 25 03:07:00 shaunsputer insmod: /lib/modules/2.4.26/kernel/drivers/cdrom/cm206.o.gz: insmod block-major-32 failed

It also seems to list other cd rom modules, which is weird :s I haven't been doing anything with CD rom's at all

Code:

Jul 25 02:17:26 shaunsputer modprobe: modprobe: Can't locate module sound-slot-1
Jul 25 02:17:26 shaunsputer modprobe: modprobe: Can't locate module sound-service-1-0
Jul 25 02:17:26 shaunsputer modprobe: modprobe: Can't locate module sound-slot-1
Jul 25 02:17:26 shaunsputer modprobe: modprobe: Can't locate module sound-service-1-0
Jul 25 02:17:52 shaunsputer modprobe: modprobe: Can't locate module sound-slot-1
Jul 25 02:17:52 shaunsputer modprobe: modprobe: Can't locate module sound-service-1-0
Jul 25 02:17:52 shaunsputer modprobe: modprobe: Can't locate module sound-slot-1
Jul 25 02:17:52 shaunsputer modprobe: modprobe: Can't locate module sound-service-1-0
Jul 25 02:20:04 shaunsputer modprobe: modprobe: Can't locate module sound-slot-1
Jul 25 02:20:04 shaunsputer modprobe: modprobe: Can't locate module sound-service-1-0
Jul 25 02:20:04 shaunsputer modprobe: modprobe: Can't locate module sound-slot-1
Jul 25 02:20:04 shaunsputer modprobe: modprobe: Can't locate module sound-service-1-0

I have no idea how to fix any of this, all confusing to me

I've tried searching in modules.conf and in the rc.d files, cant find anything

Any help appreciated

LadFromWales85 · 07-26-2004, 04:35 PM

Can anyone be of any help to me?

keefaz · 07-26-2004, 08:19 PM

Maybe something wrong with your /etc/modules.conf

Try as root :

depmod -a

LadFromWales85 · 07-27-2004, 04:02 PM

Tried that, didnt solve the problem

I've discovered that when it spams the information about loading modules for cd rom's, my pc locks up for 5-10 seconds, which is very annoying, and I cant find out whats triggering it

Cedrik · 07-28-2004, 05:10 AM

Did you try to disable hotplug (chmod -x /etc/rc.d/rc.hotplug) or if you keep it enabled, did you try to put the concerning modules in /etc/hotplug/blacklist ?