Re: Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended)
From: Thomas Gleixner <hidden>
Date: 2009-02-09 12:04:19
Also in:
lkml
Possibly related (same subject, not in this thread)
- 2009-01-22 · Re: Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended) · Paul Collins <hidden>
- 2009-01-21 · Re: Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended) · Rafael J. Wysocki <hidden>
- 2009-01-21 · Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended) · Paul Collins <hidden>
On Sun, 8 Feb 2009, Rafael J. Wysocki wrote:
On Sunday 08 February 2009, Paul Collins wrote:quoted
Paul Collins [off-list ref] writes:quoted
"Rafael J. Wysocki" [off-list ref] writes:quoted
On Wednesday 21 January 2009, Paul Collins wrote:quoted
Got a couple of these on a PowerBook running 2.6.29-rc2 either during suspend or resume -- it's hard to tell. (The suspend message is timestamped in syslog with the time I resumed, so I guess it was buffered along with the subsequent "Badness" messages.)Please check if the patch from http://lkml.org/lkml/2009/1/13/144 fixes the problem for you.It does not fix the problem.I'm also getting this warning since 2.6.28.1, which incorporated commit 1c5745aa380efb6417b5681104b007c8612fb496 ("sched_clock: prevent scd->clock from moving backwards, take #2") as commit e268dcdd404f4558cdd24c8ecede3e064df8fa33, this being the patch that introduced the WARN_ON(timekeeping_suspended) check.Hm, I thought the timekeeping suspend problem was fixed in this commit. Ingo?
The commit fixed the problem with sched_clock, but it does not fix problems where other parts of the kernel call timekeeping functions _AFTER_ timekeeping has been suspended. Thanks, tglx