> >> On Wed, Oct 29, 2014 at 09:08:46AM -0600, Jens Axboe wrote: > >>>> Another test server with MPT SCSI RAID has similar problem, > >>>> scsi_mode.use_blk_mq=0 cures it but I can not get good trace (no serail > >>>> console). 3.18.0-rc2-00043-gf7e87a4 was tested there. > >>> > >>> The first issue looks like scsi cdrom and error handling, it must be > >>> leaking > >>> requests hence we hang on allocation of a new one. cciss doesn't use > >>> blk_mq > >>> regardless of the scsi setting. Does the mpt box also have a libata driven > >>> cdrom? > >> > >> cciss does use scsi for CDROMs and other external devices, it is a bit > >> of a mess. > >> > >> Meelis, did you also test scsi-mq on 3.17 and this is a regression, or > >> was 3.18-rc2 the first kernel you tested? > > > > Both machines ran 3.17 successfully. I turned on scsi-mq option as soon > > as it appeared in Kconfig as a new option. But I am not sure whan the > > option appeared, before or after 3.17 release. > > So just to be fully clear, you never enabled scsi-mq on 3.17? To do > that, you would have had to add a scsi_mod.use_blk_mq=1 boot parameter. > The scsi-mq kconfig option did not show up until after 3.17 release.
Re-tested DL380G3 with 3.17 and manual scsi_mod.use_blk_mq=1 option. The problem happens with 3.17 too with blk-mq. -- Meelis Roos (mr...@linux.ee) -- 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
