On Tue, 22 Apr 2014, Matthieu CASTET wrote:
> Yes, but we can ignore the first "Not-ready to ready change" event
> after resume.
>
> In fact after reset, we call usb_stor_reset_resume that do a
> scsi_report_bus_reset.
> This will set the flag expecting_cc_ua in scsi layer and the scsi layer
> will ignore the first unit attention.
>
> But the commit dfcf7775815504d13a1d273073810058caf84b9d change the
> logic and we don't ignore unit attention if "sshdr.asc == 0x28 &&
> sshdr.ascq == 0x00" ("Not-ready to ready").
Good analysis.
> > In any case, the SCSI people will probably argue that ignoring such
> > events would not be safe. And if it's not safe to ignore those events
> > during normal operation then it's not safe to ignore them at resume
> > time.
> >
> > If you want to discuss the matter any further, you should post to the
> > linux-scsi mailing list. There's not much we can do about it at the
> > USB level -- although perhaps we could turn off the erroneous
> > "removable" indicator.
> Thanks,
>
> I will continue the discution on linux-scsi ML.
Inform them that the dfcf77758155 commit caused a regression on your
system.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
