[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTinBwfLXi0Bv0_gzSWRsdDPzHFQFZFwEYjbwkNs4@mail.gmail.com>
Date: Fri, 10 Sep 2010 19:53:31 +0800
From: Jeff Chua <jeff.chua.linux@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Nico Schottelius <nico-nospam@...ottelius.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Nico Schottelius <nico-linux-20100709@...ottelius.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Florian Pritz <flo@...n.at>,
Suresh Siddha <suresh.b.siddha@...el.com>, stable@...nel.org,
Ingo Molnar <mingo@...e.hu>
Subject: Re: 2.6.36-rc3 suspend issue (was: 2.6.35-rc4 / X201 issues)
On Fri, Sep 10, 2010 at 3:48 PM, Peter Zijlstra <peterz@...radead.org> wrote:
> On Fri, 2010-09-10 at 13:36 +0800, Jeff Chua wrote:
>>
>> I've bisected and it's pointing to the following commit causing the
>> errors after resume. Reverting the commit solves the problem.
>"the errors" being those at the end of this email?
Yes (partial). Attached is the detailed kernel log that I just
captured with the commit cd7240c0b900eb6d690ccee088a6c9b46dae815a
applied.
> That just doesn't make any sense, the TSC restore code doesn't involve
> acpi, nor does it actually schedule.
I don't know enough, but whatever it is, reverting the patch makes all
the errors go away!
I've "re-verified" that's the case by reverting/reapplying the same commit.
Jeff
Download attachment "kernel" of type "application/octet-stream" (61728 bytes)
Powered by blists - more mailing lists