On Wed, Apr 16, 2014 at 12:33 AM, Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx> wrote: > On Wed, 2014-04-16 at 16:30 +1000, Benjamin Herrenschmidt wrote: >> On Tue, 2014-04-15 at 18:09 -0600, Bjorn Helgaas wrote: >> > >> > Thanks for the example. Please open a bug report at >> > http://bugzilla.kernel.org and attach the complete dmesg logs before >> > and after Yinghai's patch. >> > >> > Having the complete logs helps me answer questions myself without >> > having to bother you, and it also helps me figure out whether we can >> > improve our logging to make it easier to diagnose problems like this. >> >> Unfortunately, for a *little while* longer (hint !) we can't publish >> a complete log from a Power8 machine, but we should be able to include >> everything remotely related to PCI. > > Hrm, actually, I'm not sure we can disclose the device details just yet, > so let's just hide the vendor/device ID to make the lawyers happy and > you can print all the rest. Sure, no problem (and it looks like Guo has done just that with https://bugzilla.kernel.org/show_bug.cgi?id=74151). I'm pretty sure this problem is not specific to your secret hardware; it should be reproducible on any hardware with similar apertures and similar BARs. I am a little concerned about the PE implications, but I'm ignoring that for now until we sort out the first-order problem of getting the allocation scheme to work. -- 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
