Please provide the mpt2sas driver version that you are also using. Please set the driver logging level to 0x421F8 (echo 0x421F8 > /sys/module/mpt2sas/parameters/logging_level) and the scsi logging level to 0x180000F1 (echo 0x180000F1 > /proc/sys/dev/scsi/logging_level) and recreate the issue and provide the var/log/message. Regards, Nagalakshmi -----Original Message----- From: linux-scsi-owner@xxxxxxxxxxxxxxx [mailto:linux-scsi-owner@xxxxxxxxxxxxxxx] On Behalf Of Ayman El-Khashab Sent: Tuesday, February 14, 2012 6:46 PM To: linux-scsi@xxxxxxxxxxxxxxx Subject: need help solving mpt2sas target unplug can hang worker thread I'm doing this on powerpc/4xx (if that matters). Basically I can normally hot-plug or hot-remove disks from the mpt2sas just fine. It is easy to replicate on my system if I unplug the drive during the enumeration process. Based on what I see, I gather it is in the scsi layer rather than the mpt2sas driver, but I don't have that much experience in the scsi driver to be certain. There are 2 cases that cause this ... 1) Device never finishes the initial enumerate sequence because there is something wrong with the drive, firmware on the drive, etc. 2) The drive was unplugged before the enumeration completes. *MAYBE* this is addressed by the null pointer dereference patches I've seen posted. In any case, I get the thread dumping every 120s, I cannot remove the driver module from the kernel. My only option is to reboot. It would be great if it didn't happen at all, but even if I can reset the controller and get things back to a happier time, that would be perfect. Any tips for how I might accomplish that or is there a particular patch I should take a look at / apply? Thanks Ayman -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
