From: Shawn Guo <shawn.guo@linaro.org>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Richard Zhu <r65037@freescale.com>, <kernel@pengutronix.de>,
Bjorn Helgaas <bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: The imx6q suspend/resume is broken on 3.16-rc due to PCIe
Date: Wed, 25 Jun 2014 14:12:40 +0800 [thread overview]
Message-ID: <20140625061238.GA3242@dragon> (raw)
In-Reply-To: <1403626435.4230.17.camel@weser.hi.pengutronix.de>
On Tue, Jun 24, 2014 at 06:13:55PM +0200, Lucas Stach wrote:
> Hi Shawn,
>
> Am Dienstag, den 24.06.2014, 23:36 +0800 schrieb Shawn Guo:
> > Hi Lucas,
> >
> > I found that imx6q suspend/resume is broken on 3.16-rc, and it works
> > just fine if PCIe support is built out. However the issue was not
> > exposed on 3.15, so I suspect the PCIe driver change merged in 3.16
> > is part of the cause.
> >
> I don't yet see why any of the changes to the designware/imx6 host
> driver would cause such failures.
>
> Which board are you doing your testing on? What devices are connected to
> the PCIe bus? In what way does it break system resume, complete hang?
It's on imx6q-sabresd without any PCIe device connected. Right, it's a
complete hang after enabling non-boot CPUs.
...
Enabling non-boot CPUs ...
CPU1: Booted secondary processor
CPU1 is up
CPU2: Booted secondary processor
CPU2 is up
CPU3: Booted secondary processor
CPU3 is up
<*** hang here ***>
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: The imx6q suspend/resume is broken on 3.16-rc due to PCIe
Date: Wed, 25 Jun 2014 14:12:40 +0800 [thread overview]
Message-ID: <20140625061238.GA3242@dragon> (raw)
In-Reply-To: <1403626435.4230.17.camel@weser.hi.pengutronix.de>
On Tue, Jun 24, 2014 at 06:13:55PM +0200, Lucas Stach wrote:
> Hi Shawn,
>
> Am Dienstag, den 24.06.2014, 23:36 +0800 schrieb Shawn Guo:
> > Hi Lucas,
> >
> > I found that imx6q suspend/resume is broken on 3.16-rc, and it works
> > just fine if PCIe support is built out. However the issue was not
> > exposed on 3.15, so I suspect the PCIe driver change merged in 3.16
> > is part of the cause.
> >
> I don't yet see why any of the changes to the designware/imx6 host
> driver would cause such failures.
>
> Which board are you doing your testing on? What devices are connected to
> the PCIe bus? In what way does it break system resume, complete hang?
It's on imx6q-sabresd without any PCIe device connected. Right, it's a
complete hang after enabling non-boot CPUs.
...
Enabling non-boot CPUs ...
CPU1: Booted secondary processor
CPU1 is up
CPU2: Booted secondary processor
CPU2 is up
CPU3: Booted secondary processor
CPU3 is up
<*** hang here ***>
Shawn
next prev parent reply other threads:[~2014-06-25 6:12 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 [this message]
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
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=20140625061238.GA3242@dragon \
--to=shawn.guo@linaro.org \
--cc=bhelgaas@google.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 \
/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.