All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawn.guo@freescale.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Richard Zhu <r65037@freescale.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	Shawn Guo <shawn.guo@linaro.org>,
	"Fabio Estevam" <festevam@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: The imx6q suspend/resume is broken on 3.16-rc due to PCIe
Date: Mon, 7 Jul 2014 21:55:03 +0800	[thread overview]
Message-ID: <20140707135502.GR30239@dragon> (raw)
In-Reply-To: <1404724251.4587.20.camel@weser.hi.pengutronix.de>

On Mon, Jul 07, 2014 at 11:10:51AM +0200, Lucas Stach wrote:
> Hi Shawn,
> 
> Over the weekend I tried to reproduce your problem on a SabreSD board,
> but wasn't able to trigger the issue. 3.16-rc3 with PCIe active works
> just fine over a suspend and resume cycle for me.

That's strange.  In my setup, PCIe support is enabled in kernel and DT,
but I do not have a PCIe device connected to the board.

> 
> One possibly relevant difference is that I've booted with NFSroot, while
> it seems you are using a SATA connected device. Is this right?

I have a SATA disk connected, but did boot with NFSroot.

> If so,
> can you test if it works if you boot from SDcard or the like? This might
> be relevant as PCIe and SATA share some clocks.

I tried to disable SATA support completely, but it doesn't help.

$ echo mem > /sys/power/state
[  410.052595] PM: Syncing filesystems ... done.
[  410.150033] PM: Preparing system for mem sleep
[  410.207963] Freezing user space processes ... (elapsed 0.004 seconds) done.
[  410.219796] Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.
[  410.230243] PM: Entering mem sleep
[  410.316574] PM: suspend of devices complete after 79.461 msecs
[  410.322498] PM: suspend devices took 0.090 seconds
[  410.332655] PM: late suspend of devices complete after 5.338 msecs


Shawn

WARNING: multiple messages have this Message-ID (diff)
From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: The imx6q suspend/resume is broken on 3.16-rc due to PCIe
Date: Mon, 7 Jul 2014 21:55:03 +0800	[thread overview]
Message-ID: <20140707135502.GR30239@dragon> (raw)
In-Reply-To: <1404724251.4587.20.camel@weser.hi.pengutronix.de>

On Mon, Jul 07, 2014 at 11:10:51AM +0200, Lucas Stach wrote:
> Hi Shawn,
> 
> Over the weekend I tried to reproduce your problem on a SabreSD board,
> but wasn't able to trigger the issue. 3.16-rc3 with PCIe active works
> just fine over a suspend and resume cycle for me.

That's strange.  In my setup, PCIe support is enabled in kernel and DT,
but I do not have a PCIe device connected to the board.

> 
> One possibly relevant difference is that I've booted with NFSroot, while
> it seems you are using a SATA connected device. Is this right?

I have a SATA disk connected, but did boot with NFSroot.

> If so,
> can you test if it works if you boot from SDcard or the like? This might
> be relevant as PCIe and SATA share some clocks.

I tried to disable SATA support completely, but it doesn't help.

$ echo mem > /sys/power/state
[  410.052595] PM: Syncing filesystems ... done.
[  410.150033] PM: Preparing system for mem sleep
[  410.207963] Freezing user space processes ... (elapsed 0.004 seconds) done.
[  410.219796] Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.
[  410.230243] PM: Entering mem sleep
[  410.316574] PM: suspend of devices complete after 79.461 msecs
[  410.322498] PM: suspend devices took 0.090 seconds
[  410.332655] PM: late suspend of devices complete after 5.338 msecs


Shawn

  reply	other threads:[~2014-07-07 14:10 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 15:36 The imx6q suspend/resume is broken on 3.16-rc due to PCIe Shawn Guo
2014-06-24 15:36 ` Shawn Guo
2014-06-24 16:13 ` Lucas Stach
2014-06-24 16:13   ` Lucas Stach
2014-06-25  6:12   ` Shawn Guo
2014-06-25  6:12     ` Shawn Guo
2014-06-24 19:37 ` Fabio Estevam
2014-06-24 19:37   ` Fabio Estevam
2014-06-25  6:22   ` Shawn Guo
2014-06-25  6:22     ` Shawn Guo
2014-06-25 10:50     ` Fabio Estevam
2014-06-25 10:50       ` Fabio Estevam
2014-06-25 10:50       ` Lucas Stach
2014-06-25 10:50         ` Lucas Stach
2014-06-25 12:53         ` Shawn Guo
2014-06-25 12:53           ` Shawn Guo
2014-06-26  8:43           ` Lucas Stach
2014-06-26  8:43             ` Lucas Stach
2014-06-28 14:37             ` Shawn Guo
2014-06-28 14:37               ` Shawn Guo
2014-06-30 13:44               ` Lucas Stach
2014-06-30 13:44                 ` Lucas Stach
2014-07-01  6:51                 ` Shawn Guo
2014-07-01  6:51                   ` Shawn Guo
2014-07-07  9:10                   ` Lucas Stach
2014-07-07  9:10                     ` Lucas Stach
2014-07-07 13:55                     ` Shawn Guo [this message]
2014-07-07 13:55                       ` Shawn Guo
2014-07-16  6:55                       ` Shawn Guo
2014-07-16  6:55                         ` Shawn Guo
2014-07-17 13:55                         ` Lucas Stach
2014-07-17 13:55                           ` Lucas Stach
2014-07-18  2:11                           ` Hong-Xing.Zhu
2014-07-18  2:11                             ` Hong-Xing.Zhu at freescale.com
2014-07-18  9:21                             ` Lucas Stach
2014-07-18  9:21                               ` Lucas Stach
2014-07-21  2:50                               ` Shawn Guo
2014-07-21  2:50                                 ` Shawn Guo
2014-07-21  2:55                                 ` Fabio Estevam
2014-07-21  2:55                                   ` Fabio Estevam
2014-07-21  3:19                                   ` Shawn Guo
2014-07-21  3:19                                     ` Shawn Guo
2014-06-25 12:46     ` Shawn Guo
2014-06-25 12:46       ` Shawn Guo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140707135502.GR30239@dragon \
    --to=shawn.guo@freescale.com \
    --cc=bhelgaas@google.com \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=r65037@freescale.com \
    --cc=shawn.guo@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.