It looks like I made an oops when I split out the DMA pool into a
separate file from drivers/scsi/scsi.c at about line 2272:
}
generic->write_proc = proc_scsi_gen_write;
#endif
scsi_loadable_module_flag = 1;
- if( scsi_init_minimal_dma_pool() == 0 )
+ if( scsi_init_minimal_dma_pool() != 0 )
{
return 1;
}
This also needs to be moved up ahead of the initialization of the /proc
stuff.
-Eric
----- Original Message -----
From: "Matthew Dharm" <[EMAIL PROTECTED]>
To: "The Linux SCSI list" <[EMAIL PROTECTED]>
Sent: Monday, January 24, 2000 12:05 AM
Subject: 2.3.41pre1 SCSI module problems
> 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]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
