On Thu, Jun 26, 2014 at 10:43:49AM +0200, Lucas Stach wrote: > Am Mittwoch, den 25.06.2014, 20:53 +0800 schrieb Shawn Guo: > > On Wed, Jun 25, 2014 at 12:50:52PM +0200, Lucas Stach wrote: > > > Am Mittwoch, den 25.06.2014, 07:50 -0300 schrieb Fabio Estevam: > > > > On Wed, Jun 25, 2014 at 3:22 AM, Shawn Guo <shawn.guo@xxxxxxxxxx> wrote: > > > > > > > > > Please test against v3.16-rc1 or -rc2. The breakage on linux-next > > > > > should be another issue. > > > > > > > > Yes, I see it now. Tested on -rc2 and suspend/resume works with PCI > > > > driver removed. > > > > > > Can you please send me a dmesg from a working boot? > > > > What do you mean by "working boot"? Boot is always working. What fails > > is system resuming. > > > > Shawn > > > Oops, what I meant is a dmesg after a working resume (from kernel 3.15). > I can see how failing to resume from L2 can cause the hang and we should > really implement the PHY PD toggling in the pcie driver, but I would > like to understand why you don't hit this on 3.15. Sorry, Lucas. I just noticed that in my 3.15 testing PCIe is not enabled in device tree at all. So the issue should have already been there before your changes to PCIe driver. Shawn -- 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
