On Sat, Apr 20, 2013 at 05:46:52PM +0200, Jiri Slaby wrote: > Hi, > > my machine does not wake from suspend to RAM on my box running the -next > kernel. The last thing I see is "Disabling non-boot CPUs ...". I > bisected it to this commit: > > commit 7ec98e15aa049b7a2ca73485f31cf4f90c34e2dd > Author: Thomas Gleixner <t...@linutronix.de> > Date: Thu Feb 21 22:51:39 2013 +0000 > > timekeeping: Delay update of clock->cycle_last > > > Reverting that one on the top of -next-20130419 makes it work again. > > > I also tried it inside a VM using suspend to disk. There, it behaves > like it takes a minute or so to wake up. So I tried to wait on the real > HW too, but it never resumes there.
Right, and I'm seeing it here too but it sometimes does resume after about a minute or so and sometimes it doesn't. Reverting the patch by hand ontop of tip/master fixes the issue here too. Btw, Ingo, remember how I was telling you that I'm seeing temporary lockups with tip/master and resume issues with the last line being "Disabling non-boot CPUs ..." http://marc.info/?l=linux-kernel&m=136610574502492 - this commit was the culprit. Good job Jiri. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
