From: Peter Zijlstra <peterz@infradead.org>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Nico Schottelius <nico-nospam@schottelius.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Nico Schottelius <nico-linux-20100709@schottelius.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Florian Pritz <flo@xssn.at>,
Suresh Siddha <suresh.b.siddha@intel.com>,
stable@kernel.org, Ingo Molnar <mingo@elte.hu>,
"Brown, Len" <lenb@kernel.org>
Subject: Re: 2.6.36-rc3 suspend issue (was: 2.6.35-rc4 / X201 issues)
Date: Fri, 10 Sep 2010 14:05:53 +0200 [thread overview]
Message-ID: <1284120353.402.39.camel@laptop> (raw)
In-Reply-To: <AANLkTinBwfLXi0Bv0_gzSWRsdDPzHFQFZFwEYjbwkNs4@mail.gmail.com>
On Fri, 2010-09-10 at 19:53 +0800, Jeff Chua wrote:
> On Fri, Sep 10, 2010 at 3:48 PM, Peter Zijlstra <peterz@infradead.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.
next prev parent reply other threads:[~2010-09-10 12:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 5:36 2.6.36-rc3 suspend issue (was: 2.6.35-rc4 / X201 issues) Jeff Chua
2010-09-10 7:48 ` Peter Zijlstra
2010-09-10 11:53 ` Jeff Chua
2010-09-10 12:05 ` Peter Zijlstra [this message]
2010-09-10 17:19 ` Jeff Chua
2010-09-10 20:32 ` [PATCH] x86, tsc: Fix a preemption leak in restore_sched_clock_state() Peter Zijlstra
2010-09-10 21:01 ` Suresh Siddha
2010-09-11 0:59 ` Jeff Chua
2010-09-11 7:49 ` [tip:sched/urgent] " tip-bot for Peter Zijlstra
2010-09-13 7:42 ` Nico Schottelius
2010-09-13 8:46 ` Ingo Molnar
2010-09-13 22:56 ` Jeff Chua
2010-09-15 8:03 ` Nico Schottelius
2010-09-28 11:59 ` 2.6.36-rc3-00464-g84e1d83 resume issue (was: [tip:sched/urgent] x86, tsc: Fix a preemption leak in restore_sched_clock_state()) Nico Schottelius
-- strict thread matches above, loose matches on Subject: below --
2010-07-09 17:04 2.6.35-rc4 / X201 issues Nico Schottelius
2010-07-09 17:29 ` Jesse Barnes
2010-09-06 7:17 ` 2.6.36-rc3 suspend issue (was: 2.6.35-rc4 / X201 issues) Nico Schottelius
2010-09-06 8:49 ` Nico Schottelius
2010-09-06 13:50 ` Jeff Chua
2010-09-06 18:37 ` Rafael J. Wysocki
2010-09-07 3:42 ` Jeff Chua
2010-09-07 21:48 ` Rafael J. Wysocki
2010-09-07 22:50 ` Nico Schottelius
2010-09-07 23:28 ` Rafael J. Wysocki
2010-09-08 6:21 ` Nico Schottelius
2010-09-08 22:27 ` Rafael J. Wysocki
2010-09-10 8:26 ` Nico Schottelius
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=1284120353.402.39.camel@laptop \
--to=peterz@infradead.org \
--cc=flo@xssn.at \
--cc=jbarnes@virtuousgeek.org \
--cc=jeff.chua.linux@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nico-linux-20100709@schottelius.org \
--cc=nico-nospam@schottelius.org \
--cc=rjw@sisk.pl \
--cc=stable@kernel.org \
--cc=suresh.b.siddha@intel.com \
--cc=torvalds@linux-foundation.org \
/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