On 04/13/2016 09:29 AM, Sudeep Holla wrote: > > > On 13/04/16 14:21, Bjorn Helgaas wrote: >> On Wed, Apr 13, 2016 at 10:58:18AM +0100, Sudeep Holla wrote: >>> Hi, >>> >>> (sorry for replying on the old thread, but I found it could be related >>> to the issue >>> I have now) >>> >>> On Tue, Jul 28, 2015 at 10:29 PM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> >>> wrote: > > [...] > >>>>> >>>>> Our latest U-Boot is 1.15.15, but U-Boot 1.15.12 is already a good >>>>> version to use. Are you running any PCIe traffic test when the error >>>>> happens? >>>> >>>> Nope, the machine was either idle or running a reboot test; no PCIe >>>> stress >>>> test or anything. >>>> >>> >>> Was there any conclusion on this ? >>> I am having similar issue[1] on my Juno with sky2 PCIe driver during >>> reboot. >> >> We found that the unhandled faults occurred when using an extender >> card. After removing the extender card, we didn't see the faults any >> more. >> > > Thanks for the response. It's not related then, I saw report referencing > reboot tests and hence linked them together. Sorry for the noise. For the record, I've had success with this cable on X-Gene: http://www.amazon.com/PCI-E-Riser-Flexible-Ribbon-Extension/dp/B00H8VVD00?ie=UTF8&psc=1&redirect=true&ref_=oh_aui_search_detailpage But it's hit or miss. The only public platform where I've been reliably able to use an extender cable so far is AMD Seattle. On that platform, the PCIe IP is so rock solid that I can talk to very funky PCIe IP I've implemented myself in a FPGA (and I can see link quality is fine too). There's one other non-public platform so far where PCIe extenders work without a single hitch as well, and a number where more work is needed. Jon. -- Computer Architect -- 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
