Hey, On 06/15/2016 01:34 PM, Brian King wrote:
Mauricio was looking at this, adding him to cc. We did have a KVM config where we could reproduce this issue as well, I think with some PCI passthrough adapters. Mauricio - do you have any more details about the KVM config that reproduced this issue and did you ever try to reproduce this with an upstream kernel?
It's KVM guest w/ SLES 12 SP1 + kernel updates (3.12.53-60.30 introduced the error) and PCI passthrough of Emulex FC and FCoE adapters, connected to 4 storage systems (DS8000, XIV, SVC, and FlashSystem 840). It seems only the XIV LUNs never hit the problem, but it didn't seem to be storage-specific, as FS840 LUNs had a mix of hit/not-hit the problem. One thing is that all paths of a LUN were either failed or not - no mix within a LUN. Unfortunately not too much analysis was performed on this system at the time -- Hannes had already made good progress w/ the customer, and some test kernel builds that resolved the issue were made available soon. Now that the topic is under discussion, I've asked for some time slots on that system, so we can test an upstream kernel and try to reproduce the problem and analyze it more closely. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- 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