I just tried 2.3.41pre1 and found a problem using scsi as a module. When
I try to insmod/modprobe scsi_mod, I get a device or resource busy error.
The /proc/scsi/scsi entry is created, but when I try to cat it I get a
kernel OOPS.
Repeated attempts to insmod/modprobe the module causes multiple /proc
entries to be created, all with the same name. Looking at the code, it
would appear the the init code which creates this entry occurs before it's
determined if the load is going to be successful -- I consider this to be
a separate problem from the one which might be causing the module to fail
to load.
Matt Dharm
--
Matthew Dharm Home: [EMAIL PROTECTED]
Engineer, Qualcomm, Inc. Work: [EMAIL PROTECTED]
God, root, what is difference?
-- Pitr
User Friendly, 11/11/1999
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
