[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070911013512.8d62220e.akpm@linux-foundation.org>
Date: Tue, 11 Sep 2007 01:35:12 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Thomas Gleixner <tglx@...utronix.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
john stultz <johnstul@...ibm.com>, Ingo Molnar <mingo@...e.hu>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: clockevents: fix resume logic
On Tue, 11 Sep 2007 01:20:05 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Tue, 11 Sep 2007 09:47:20 +0200 Thomas Gleixner <tglx@...utronix.de> wrote:
>
> > On Tue, 2007-09-11 at 09:23 +0200, Thomas Gleixner wrote:
> > > > I went back to the original patch which I sent to Linus and it matches
> > > > 18de5bc4c1f1f1fa5e14f354a7603bd6e9d4e3b6. So all I can think is that there
> > > > must have been something else in the tree which I tested which fixed the
> > > > bug which 18de5bc4c1f1f1fa5e14f354a7603bd6e9d4e3b6 introduced. argh.
> > > >
> > > > Can you think what would cause the symptoms which I described?
> > >
> > > It seems that time is not updated. Timer interrupt not active or some
> > > other odd thing. I figure out what's going on when I find a box which
> > > exposes the problem.
>
> 2.6.22-rc6-mm1's git-acpi.patch contains something which fixes this bug.
Len's current tree fixes it too. Maybe we just need to merge the acpi tree?
46 files changed, 4168 insertions(+), 2224 deletions(-)
I'll let Len do that ;)
Ho hum. I guess I could do a git-bisect on the acpi tree. Getting a bit dull.
-
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