From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.16-rc4
Date: Thu, 7 Aug 2014 21:14:42 -0500 [thread overview]
Message-ID: <20140808021442.GA22811@saruman.home> (raw)
In-Reply-To: <alpine.DEB.2.02.1408072210300.5770@utopia.booyaka.com>
Hi,
On Thu, Aug 07, 2014 at 10:21:23PM +0000, Paul Walmsley wrote:
> On Fri, 1 Aug 2014, Tony Lindgren wrote:
>
> > * Paul Walmsley <paul@pwsan.com> [140731 12:29]:
> > > On Thu, 31 Jul 2014, Tony Lindgren wrote:
> > >
> > > > * Paul Walmsley <paul@pwsan.com> [140730 00:55]:
> > > > > On Tue, 29 Jul 2014, Tony Lindgren wrote:
> > > > >
> > > > > > The following patch should fix the tests above for 3530es3beagle.
> > > > > > Care to test and ack as I don't have one?
> > > > >
> > > > > 3530es3beagle retention dynamic idle tests hang on next-20140729. (Maybe
> > > > > other boards fail too - haven't tested any others).
> > > >
> > > > I just checked that today's linux next works for off-idle and
> > > > wake-up events for at least 37xx evm.
> > >
> > > I ran the full set of tests across all boards. The only board that passed
> > > the dynamic idle testing on next-20140729 was the 3730beaglexm.
> > >
> > > http://www.pwsan.com/omap/testlogs/next_20140729/20140730124836/README.txt
> > >
> > > 37xxevm hangs on the first suspend entry:
> > >
> > > http://www.pwsan.com/omap/testlogs/next_20140729/20140730124836/pm/37xxevm/37xxevm_log.txt
> > >
> > > If I find some extra time, I'll set up a bisection run.
> >
> > OK that sounds like some driver suspend regression that needs
> > to be tracked down. I'm seeing it on my 37xx evm also with
> > linux next too.
>
> It's commit a71e3c37960ce5f9c6a519bc1215e3ba9fa83e75:
>
> Author: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> Date: Wed Jul 23 16:47:31 2014 -0300
>
> net: phy: Set the driver when registering an MDIO bus device
>
> mdiobus_register() registers a device which is already bound to a driver.
> Hence, the driver pointer should be set properly in order to track down
> the driver associated to the MDIO bus.
>
> This will be used to allow ethernet driver to pin down a MDIO bus driver,
> preventing it from being unloaded while the PHY device is running.
>
> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
> Tested-by: Florian Fainelli <f.fainelli@gmail.com>
> Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
>
> What's bad is that this went in late during v3.16-rc fixes. So now v3.16
> itself is broken, and there's no way to fix it.
we have stable releases for that.
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140807/828d02d0/attachment.sig>
next prev parent reply other threads:[~2014-08-08 2:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-06 23:41 OMAP baseline test results for v3.16-rc4 Paul Walmsley
2014-07-07 8:02 ` Tony Lindgren
2014-07-14 17:28 ` Paul Walmsley
2014-07-15 6:04 ` Tony Lindgren
2014-07-15 19:56 ` Paul Walmsley
2014-07-25 19:14 ` Paul Walmsley
2014-07-29 6:42 ` Tony Lindgren
2014-07-29 8:25 ` Paul Walmsley
2014-07-29 8:49 ` Tony Lindgren
2014-07-29 12:32 ` Paul Walmsley
2014-07-29 12:57 ` Paul Walmsley
2014-07-29 14:53 ` Tony Lindgren
2014-07-29 19:37 ` Paul Walmsley
2014-07-30 5:39 ` Tony Lindgren
2014-07-30 7:53 ` Paul Walmsley
2014-07-31 13:11 ` Tony Lindgren
2014-07-31 19:27 ` Paul Walmsley
2014-08-01 7:10 ` Tony Lindgren
2014-08-01 7:52 ` Tony Lindgren
2014-08-07 22:21 ` Paul Walmsley
2014-08-08 2:14 ` Felipe Balbi [this message]
2014-08-08 6:11 ` Paul Walmsley
2014-08-08 14:34 ` Felipe Balbi
2014-08-08 23:39 ` Paul Walmsley
2014-08-09 2:49 ` Felipe Balbi
2014-08-08 2:29 ` Fabio Estevam
2014-08-08 6:14 ` Paul Walmsley
2014-08-09 12:41 ` Ezequiel Garcia
2014-07-31 13:12 ` Tero Kristo
2014-07-29 8:50 ` Paul Walmsley
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=20140808021442.GA22811@saruman.home \
--to=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).