Re: Linux kernels 4.3+ mess up MPT2SAS configs
> "Martin" == Martin K Petersen writes: > "John" == John Stoffel writes: John> I've got an LSI MPT2SAS controller in my home system, great board, John> running well. When I try to use kernels newer than approximately John> 4.3.0, the default Kconfig entry goes away because of what looks John> like a merge of the mpt2sas and mpt3sas drivers. Martin> http://git.kernel.org/cgit/linux/kernel/git/mkp/scsi.git/commit/?h=4.4/scsi-queue Thanks, I'll test that out in a bit. Now chasing another problem where the system crashes quickly on bootup. 4.2.x has been stable, but nothing since 4.3-rc1 has successfully booted up and lasted for me. No idea why, and not looking forward to git bisect to try and figure out since it's my home NFS server with home dirs and other data which needs to be rebooted to check. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux kernels 4.3+ mess up MPT2SAS configs
> "John" == John Stoffel writes: John> I've got an LSI MPT2SAS controller in my home system, great board, John> running well. When I try to use kernels newer than approximately John> 4.3.0, the default Kconfig entry goes away because of what looks John> like a merge of the mpt2sas and mpt3sas drivers. http://git.kernel.org/cgit/linux/kernel/git/mkp/scsi.git/commit/?h=4.4/scsi-queue -- Martin K. Petersen Oracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Linux kernels 4.3+ mess up MPT2SAS configs
Hi, I've got an LSI MPT2SAS controller in my home system, great board, running well. When I try to use kernels newer than approximately 4.3.0, the default Kconfig entry goes away because of what looks like a merge of the mpt2sas and mpt3sas drivers. In my hand made 4.2.6 config I have: CONFIG_SCSI_MPT2SAS=m CONFIG_SCSI_MPT2SAS_MAX_SGE=128 # CONFIG_SCSI_MPT2SAS_LOGGING is not set # CONFIG_SCSI_MPT3SAS is not set But when I pull down the 4.4-rc3 release and do: make mrproper cp /boot/config-4.2.6 .config make oldconfig I silently get my CONFIG_SCSI_MPT2SAS entry removed, and the CONFIG_SCSI_MPT3SAS is still left unconfigured! This is a pain when you boot up and your home directory and other data files aren't available... > grep MPT .config CONFIG_PREEMPT_NOTIFIERS=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_CB710_DEBUG_ASSUMPTIONS=y # CONFIG_SCSI_MPT3SAS is not set Can we please get this fixed so that moving forward this is setup properly? Thanks, John -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
