On Mon, 9 Apr 2012, Elric Fu wrote:
> Hi Sarah,
>
> I found the reason caused the oops. It is not a xHCI driver issue but a SCSI
> core issue.
>
> 778 static int scsi_send_eh_cmnd(struct scsi_cmnd *scmd, unsigned char *cmnd,
> 779 int cmnd_size, int timeout, unsigned
> sense_bytes)
> 780 {
> 781 struct scsi_device *sdev = scmd->device;
> 782 struct scsi_driver *sdrv = scsi_cmd_to_driver(scmd);
> 783 struct Scsi_Host *shost = sdev->host;
> 784 DECLARE_COMPLETION_ONSTACK(done);
> 785 unsigned long timeleft;
> 786 struct scsi_eh_save ses;
> 787 int rtn;
>
> The oops will occur while the driver run to line 782. It was added in 3.4-rc1,
> the Commit ID is 18a4d0a22ed6c54b67af7718c305cd010f09ddf8. And
> the subject is "[SCSI] Handle disk devices which can not process medium".
>
> I am not familiar with the SCSI core. It seems like scsi_cmd_to_driver() has
> an issue. But the issue is very random. It only happened while the device
> was reset by mass storage driver due to some scsi commands failed and
> re-enumerated in device initialization process. And even if the device is
> reset, the issue doesn't always occur. So should we forward the mail to
> linux-scsi?
This definitely should be reported, along with all the available
information, on the linux-scsi list. Also, the author of the commit in
question should be CC'ed.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
