On Fri, 1 Aug 2014, Tony Lindgren wrote: > * Paul Walmsley <paul@xxxxxxxxx> [140731 12:29]: > > On Thu, 31 Jul 2014, Tony Lindgren wrote: > > > > > * Paul Walmsley <paul@xxxxxxxxx> [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@xxxxxxxxxxxxxxxxxx> 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@xxxxxxxxx> Tested-by: Florian Fainelli <f.fainelli@xxxxxxxxx> Signed-off-by: Ezequiel Garcia <ezequiel.garcia@xxxxxxxxxxxxxxxxxx> Signed-off-by: David S. Miller <davem@xxxxxxxxxxxxx> 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. As far as I can tell, this patch doesn't fix a regression. So no way it should have gone in during late -rc kernels. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
