On Wed, Oct 30, 2013 at 4:27 AM, Jiri Kosina <jkosina@xxxxxxx> wrote: > Attached is dmesg output leading to timeouts (that are cured by my > original patch in this thread) and lspci. I opened https://bugzilla.kernel.org/show_bug.cgi?id=64141 for this issue and attached your dmesg log and lspci output. > Please let me know if there is anything else I could do, or if you are > going to proceed with my patch adding the quirk. Your quirk keeps us from disabling MSIs on the device during enumeration. But even if the BIOS left MSIs enabled, there's nothing to field the MSI until after the driver claims the device. So I don't believe this has to be done as a quirk. It should work just as well to do something in the driver when it claims the device. I guess another way to say this is that I don't think we understand what the real problem is, and if we just add a quirk to work around it, we might miss the chance to fix the real problem, and we may never be able to remove the special-case code we're adding in the generic path. I know you said you tried doing something in the driver, and it didn't work. I don't know exactly what you tried, but twa_probe() looks strange to me. The other drivers I looked at do all their PCI initialization before the scsi_host_alloc() / scsi_add_host() / scsi_scan_host() stuff. But twa_probe() has PCI stuff scattered around between those three SCSI calls. In particular, it does the MSI setup way down near the end, after scsi_add_host(), which seems like just the sort of thing that could explain this problem. Bjorn -- 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
