[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1284120353.402.39.camel@laptop>
Date: Fri, 10 Sep 2010 14:05:53 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Jeff Chua <jeff.chua.linux@...il.com>
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>, "Brown, Len" <lenb@...nel.org>
Subject: Re: 2.6.36-rc3 suspend issue (was: 2.6.35-rc4 / X201 issues)
On Fri, 2010-09-10 at 19:53 +0800, Jeff Chua wrote:
> 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.
Could you try again with CONFIG_FRAME_POINTER=y, these stacks are a
terrible mess.
--
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