From: Shawn Guo <shawn.guo@freescale.com>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Fabio Estevam <festevam@gmail.com>,
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>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Lucas Stach <l.stach@pengutronix.de>,
Stephen Warren <swarren@wwwdotorg.org>
Subject: Re: The imx6q suspend/resume is broken on 3.16-rc due to PCIe
Date: Wed, 25 Jun 2014 20:46:36 +0800 [thread overview]
Message-ID: <20140625124635.GA6917@dragon> (raw)
In-Reply-To: <20140625062243.GD3242@dragon>
On Wed, Jun 25, 2014 at 02:22:44PM +0800, Shawn Guo wrote:
> On Tue, Jun 24, 2014 at 04:37:19PM -0300, Fabio Estevam wrote:
> > On Tue, Jun 24, 2014 at 12:36 PM, Shawn Guo <shawn.guo@linaro.org> wrote:
> > > 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 have just tested this on linux-next and I see that suspend/resume
> > fails even if I build a kernel without PCI support.
>
> Please test against v3.16-rc1 or -rc2. The breakage on linux-next
> should be another issue.
Yeah, the issue on linux-next is caused by commit 478850160636 (irq_work:
Implement remote queueing). And Stephen reported the issue as below.
https://lkml.org/lkml/2014/6/24/765
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: Wed, 25 Jun 2014 20:46:36 +0800 [thread overview]
Message-ID: <20140625124635.GA6917@dragon> (raw)
In-Reply-To: <20140625062243.GD3242@dragon>
On Wed, Jun 25, 2014 at 02:22:44PM +0800, Shawn Guo wrote:
> On Tue, Jun 24, 2014 at 04:37:19PM -0300, Fabio Estevam wrote:
> > On Tue, Jun 24, 2014 at 12:36 PM, Shawn Guo <shawn.guo@linaro.org> wrote:
> > > 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 have just tested this on linux-next and I see that suspend/resume
> > fails even if I build a kernel without PCI support.
>
> Please test against v3.16-rc1 or -rc2. The breakage on linux-next
> should be another issue.
Yeah, the issue on linux-next is caused by commit 478850160636 (irq_work:
Implement remote queueing). And Stephen reported the issue as below.
https://lkml.org/lkml/2014/6/24/765
Shawn
next prev parent reply other threads:[~2014-06-25 13:02 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
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 [this message]
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=20140625124635.GA6917@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 \
--cc=swarren@wwwdotorg.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.