[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <5172B86C.5030606@suse.cz>
Date: Sat, 20 Apr 2013 17:46:52 +0200
From: Jiri Slaby <jslaby@...e.cz>
To: Thomas Gleixner <tglx@...utronix.de>,
John Stultz <john.stultz@...aro.org>,
Linux-pm mailing list <linux-pm@...ts.linux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Resume does not work after timekeeping change
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 <tglx@...utronix.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.
regards,
--
js
suse labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists