RE: [SLE] SMP & AIC7880 controller
Thanks. I have got it working!!!!!! Nothing wrong with Suse or the SCSI devices. Problem solved by swopping out one of the processors. It seems that they were not the same step. Replaced it, booted the machine and SUCCESS!! This really flies !! No just have to add some more memory. i saw that the machine was swapping. Thanks for your advice. I also prefer to compile the SCSI and NIC into the kernel. Is there any performance gain/loss in doing this rather that building the modules. Schalk Klee -----Original Message----- From: C Polisher [mailto:cpolish@ns.net] Sent: Thursday, September 30, 1999 1:19 AM To: Schalk Klee Cc: suse-linux-e@suse.com Subject: Re: [SLE] SMP & AIC7880 controller
Thanks, tried both options no luck. Do you also use a conner drive. I have read that this might be the cause of my problem as well.
I haven't seen any info on Conner drives and SMP causing a problem... Can you post (the relevant portions) of your kernel configuration, and an outline of the procedure you're using to make the kernel? Did you make modules? Did you build the UP (non-SMP) kernel yourself? If it's a stock kernel, maybe there's an issue with your kernel build process. I prefer configuring the SCSI drivers into the kernel, rather than compile them as loadable modules. Keep trying, it's worth it! ---------------------My configuration: (abridged)--------------- CONFIG_EXPERIMENTAL=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set CONFIG_M586=y CONFIG_SMP=y # # General setup # # CONFIG_APM is not set # # SCSI support # CONFIG_SCSI=y CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set CONFIG_BLK_DEV_SR=y # CONFIG_BLK_DEV_SR_VENDOR is not set # CONFIG_CHR_DEV_SG is not set # CONFIG_SCSI_MULTI_LUN is not set CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_LOGGING=y # # SCSI low-level drivers # # CONFIG_SCSI_7000FASST is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AHA152X is not set # CONFIG_SCSI_AHA1542 is not set # CONFIG_SCSI_AHA1740 is not set CONFIG_SCSI_AIC7XXX=y CONFIG_AIC7XXX_TCQ_ON_BY_DEFAULT=y CONFIG_AIC7XXX_CMDS_PER_DEVICE=8 CONFIG_AIC7XXX_PROC_STATS=y CONFIG_AIC7XXX_RESET_DELAY=5 # CONFIG_SCSI_DEBUG is not set # # Filesystems # CONFIG_QUOTA=y CONFIG_PROC_FS=y CONFIG_DEVPTS_FS=y CONFIG_EXT2_FS=y # # Network File Systems # # CONFIG_CODA_FS is not set # CONFIG_NFS_FS is not set # CONFIG_NFSD is not set # CONFIG_SUNRPC is not set # CONFIG_LOCKD is not set CONFIG_SMB_FS=y # CONFIG_NCP_FS is not set # # Kernel hacking # CONFIG_MAGIC_SYSRQ=y --------------------- end configuration ------------------------ My procedure to make the kernel: make menuconfig make dep make clean make bzimage cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz cp /usr/src/linux/system.map /boot/system.map /sbin/lilo (parameters here) shutdown -r now -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Schalk Klee wrote:
Thanks for your advice. I also prefer to compile the SCSI and NIC into the kernel. Is there any performance gain/loss in doing this rather that building the modules.
Congratulations! I don't think it improves performance. There's a theoretical security issue with modules: some people have devised a means for attacking a running kernel and replacing modules with their own. It doesn't worry me -- yet. I "compile the modules in" since I know my hardware will always be SCSI so the IDE stuff and the ability to load scsi modules is wasted space. Hope that helps -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (2)
-
cpolish@ns.net
-
schalk@RUBICO.COM