On Mon, Feb 24, 2014 at 4:46 PM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote: > [+cc Rajat] > > On Mon, Feb 24, 2014 at 4:59 PM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote: >> On system with 16 PCI express hotplug slots, customer complain every slot >> will report "Command not completed in 1000 msec" during initialization. >> >> Intel says that we should only wait command complete only for >> Electromechanical Interlock Control >> Power Controller Control >> Power Indicator Control >> Attention Indicator Control > > Is there something in the spec that says this? I'm looking at section > 6.7.3.2. It says "If command completed events are supported, then > software must wait for a command to complete before issuing the next > command." It's obvious that this is conditional on the "No Command > Completed Support" bit, but I don't see anything about a connection > with the other bits you mentioned. others told me that other os does not check command complete when enabling notification. > > Is this related to an erratum in the Intel/AMD/Nvidia chipsets? If > so, we need at least a comment about that in the source, and > preferably, some sort of quirk for these chipsets. Vendor does not agree that is silicon problem. But will update EDS to state that CC will be only set when those four control bits are handled. > > This is similar to the issue Rajat is working on with > http://patchwork.ozlabs.org/patch/322387/ . I haven't merged that > yet, but I probably will. Is there any connection between that patch > and this issue? Does this issue still happen even with Rajat's patch > applied? looks like other way. The issue still happen with Rajat's patch. Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
