[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090208151122.GB5314@elte.hu>
Date: Sun, 8 Feb 2009 16:11:22 +0100
From: Ingo Molnar <mingo@...e.hu>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Paul Collins <paul@...ly.ondioline.org>,
Thomas Gleixner <tglx@...utronix.de>, linuxppc-dev@...abs.org,
linux-kernel@...r.kernel.org
Subject: Re: Badness at kernel/time/timekeeping.c:98 in pmud
(timekeeping_suspended)
* Rafael J. Wysocki <rjw@...k.pl> wrote:
> On Sunday 08 February 2009, Paul Collins wrote:
> > Paul Collins <paul@...ly.ondioline.org> writes:
> >
> > > "Rafael J. Wysocki" <rjw@...k.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?
Thomas? :-)
Ingo
--
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