Hi, I'm running kernel 2.3.49 SMP and running into a problem regarding ATAPI SCSI emulation. Sometimes it seems the modules are unloaded in the wrong order and I get stuck with a bunch of unregistered symbols and have to reboot the machine. One ATAPI CD-RW in hdc/scd0 One ATAPI CD in hdd/scd1 This are the loaded modules: ide-scsi 8268 0 (autoclean) sr_mod 12208 0 (autoclean) scsi_mod 83912 2 (autoclean) [ide-scsi sr_mod] cdrom 26716 0 (autoclean) [sr_mod] This is /etc/conf.modules: alias scd0 sr_mod alias scsi_hostadapter ide-scsi options ide-cd ignore=hdc The relevant bits of my .config: CONFIG_BLK_DEV_FD=m CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y CONFIG_BLK_DEV_IDECD=m CONFIG_BLK_DEV_IDESCSI=m CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_IDEDMA_PCI_AUTO=y CONFIG_IDEDMA_NEW_DRIVE_LISTINGS=y CONFIG_IDEDMA_PCI_EXPERIMENTAL=y CONFIG_BLK_DEV_PIIX=y CONFIG_PIIX_TUNING=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDEDMA_AUTO=y CONFIG_BLK_DEV_LOOP=m CONFIG_BLK_DEV_IDE_MODES=y CONFIG_SCSI=m CONFIG_BLK_DEV_SR=m CONFIG_SR_EXTRA_DEVS=2 CONFIG_CHR_DEV_SG=m CONFIG_SCSI_DEBUG_QUEUES=y CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_CONSTANTS=y These are the modules initialization messages (from /var/log/messages) Mar 9 06:03:19 localhost kernel: scsi0 : SCSI host adapter emulation for IDE ATAPI devices Mar 9 06:03:19 localhost kernel: scsi : 1 host. Mar 9 06:03:19 localhost kernel: Vendor: CREATIVE Model: CD-RW RW8432E Rev: 1.05 Mar 9 06:03:19 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Mar 9 06:03:19 localhost kernel: Vendor: MITSUMI Model: CD-ROM FX3400S!B Rev: u01 Mar 9 06:03:19 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Mar 9 06:03:19 localhost kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 Mar 9 06:03:19 localhost kernel: Detected scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0 Mar 9 06:03:19 localhost kernel: sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray Mar 9 06:03:20 localhost kernel: Uniform CD-ROM driver Revision: 3.06 Mar 9 06:03:20 localhost kernel: sr1: scsi3-mmc drive: 34x/34x cd/rw xa/form2 cdda tray This seems to be the normal situation, modules get removed periodically by /sbin/rmmod -as in a cron job and get loaded right back (?why?): Mar 9 06:20:00 localhost kernel: scsi : 0 hosts. Mar 9 06:20:00 localhost kernel: Uniform CD-ROM driver unloaded Mar 9 06:20:01 localhost kernel: scsi0 : SCSI host adapter emulation for IDE ATAPI devices Mar 9 06:20:01 localhost kernel: scsi : 1 host. Mar 9 06:20:01 localhost kernel: Vendor: CREATIVE Model: CD-RW RW8432E Rev: 1.05 Mar 9 06:20:01 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Mar 9 06:20:01 localhost kernel: Vendor: MITSUMI Model: CD-ROM FX3400S!B Rev: u01 Mar 9 06:20:01 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Mar 9 06:20:01 localhost kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 Mar 9 06:20:01 localhost kernel: Detected scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0 Mar 9 06:20:01 localhost kernel: sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray Mar 9 06:20:01 localhost kernel: Uniform CD-ROM driver Revision: 3.06 Mar 9 06:20:01 localhost kernel: sr1: scsi3-mmc drive: 34x/34x cd/rw xa/form2 cdda tray These are the messages when problems start: Mar 9 01:50:00 localhost kernel: scsi : 0 hosts. Mar 9 01:50:01 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_io_completion Mar 9 01:50:01 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_wait_req Mar 9 01:50:01 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_unregister_module Mar 9 01:50:01 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_block_when_processing_errors Mar 9 01:50:01 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_release_request Mar 9 01:50:01 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_allocate_request Mar 9 01:50:01 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol print_req_sense Mar 9 01:50:01 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_register_module Mar 9 01:50:01 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol print_command Mar 9 01:50:01 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_ioctl Mar 9 01:50:01 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_sleep Mar 9 01:50:01 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_free Mar 9 01:50:01 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_malloc Mar 9 01:50:03 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_io_completion Mar 9 01:50:03 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_wait_req Mar 9 01:50:03 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_unregister_module Mar 9 01:50:03 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_block_when_processing_errors Mar 9 01:50:03 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_release_request Mar 9 01:50:03 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_allocate_request Mar 9 01:50:03 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol print_req_sense Mar 9 01:50:03 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_register_module Mar 9 01:50:03 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol print_command Mar 9 01:50:03 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_ioctl Mar 9 01:50:03 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_sleep Mar 9 01:50:03 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_free Mar 9 01:50:03 localhost insmod: /lib/modules/2.3.49/scsi/sr_mod.o: unresolved symbol scsi_malloc the scsi module seems to have been removed under the sr_mod module.... After this even a /sbin/lsmod fails (with an error I forgot to write down :( Another problem, is that if I access the hdd driver using the ide layer (mount hdd) after loading the scsi modules whole hell breaks loose. Shouldn't I be prevented from doing this (like a `resource busy message` or something)? I'll be glad to provide more debug info. Thanks for any help, Rui Sousa - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED]
