From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: Possible suspend/resume regression in .32-rc?
Date: Sat, 31 Oct 2009 02:34:27 +0100 [thread overview]
Message-ID: <20091031013427.GL14091@buzzloop.caiaq.de> (raw)
Is anyone using suspend/resume with a recent git mainline kernel on PXA
or other ARM embedded boards? My platform used to suspend and resume
just fine on 2.6.31 but now as I rebased it, it fails the resume part.
Unfortunately, I can't bisect it as the platform is not mainline yet and
so I always have mandatory patches (without my platform won't do
anything) on top of the git repository. Which breaks the bisect logic.
What puzzles me is that I see the current raising at wakeup time, so at
least the processor seems to resume, but I can't see any serial console
output, just like if the kernel crashed very early after wakeup.
'no_console_suspend' didn't help either.
Does anyone use that successfully? Any idea for possible regressions?
Daniel
next reply other threads:[~2009-10-31 1:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 1:34 Daniel Mack [this message]
2009-10-31 12:56 ` Possible suspend/resume regression in .32-rc? Eric Miao
2009-10-31 16:39 ` Robert Jarzmik
2009-11-01 0:48 ` Ben Dooks
2009-11-01 19:54 ` Ryan Mallon
2009-11-01 20:22 ` Uwe Kleine-König
2009-11-01 20:54 ` Daniel Mack
2009-11-01 21:33 ` Pavel Machek
2009-11-01 22:03 ` Pavel Machek
2009-11-02 9:22 ` Haojian Zhuang
2009-11-02 9:29 ` Daniel Mack
2009-11-02 9:38 ` Pavel Machek
2009-11-02 9:54 ` Eric Miao
2009-11-02 10:48 ` Haojian Zhuang
2009-11-02 10:51 ` Pavel Machek
2009-11-02 11:18 ` Haojian Zhuang
2009-11-02 11:27 ` Daniel Mack
2009-11-02 12:22 ` Pavel Machek
2009-11-02 9:57 ` Stanislav Brabec
2009-11-03 3:31 ` Haojian Zhuang
2009-11-03 9:50 ` Stanislav Brabec
2009-11-05 5:06 ` Haojian Zhuang
2010-01-13 11:46 ` Daniel Mack
2010-01-13 13:42 ` Stanislav Brabec
2010-01-13 15:33 ` Greg KH
2009-11-01 21:13 ` Pavel Machek
2009-11-01 21:16 ` Daniel Mack
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=20091031013427.GL14091@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).