From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Paul Collins <paul@burly.ondioline.org>, Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended)
Date: Sun, 8 Feb 2009 14:39:30 +0100 [thread overview]
Message-ID: <200902081439.31548.rjw@sisk.pl> (raw)
In-Reply-To: <874oz5pmvd.fsf@burly.wgtn.ondioline.org>
On Sunday 08 February 2009, Paul Collins wrote:
> Paul Collins <paul@burly.ondioline.org> writes:
>
> > "Rafael J. Wysocki" <rjw@sisk.pl> writes:
> >
> >> On Wednesday 21 January 2009, Paul Collins wrote:
> >>> 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?
next prev parent reply other threads:[~2009-02-08 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 7:15 Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended) Paul Collins
2009-01-21 16:13 ` Rafael J. Wysocki
2009-01-22 8:19 ` Paul Collins
2009-02-08 4:35 ` Paul Collins
2009-02-08 13:39 ` Rafael J. Wysocki [this message]
2009-02-08 15:11 ` Ingo Molnar
2009-02-09 12:03 ` Thomas Gleixner
2009-02-12 6:05 ` Benjamin Herrenschmidt
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=200902081439.31548.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=paul@burly.ondioline.org \
--cc=tglx@linutronix.de \
/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