From: Sven Neumann <s.neumann@raumfeld.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Daniel Mack <daniel@caiaq.de>, Colin Cross <ccross@android.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: 2.6.35.6 fails to suspend (pxa2xx-mci.0)
Date: Fri, 08 Oct 2010 10:23:17 +0200 [thread overview]
Message-ID: <1286526197.4493.19.camel@sven> (raw)
In-Reply-To: <201010072323.05218.rjw@sisk.pl>
On Thu, 2010-10-07 at 23:23 +0200, Rafael J. Wysocki wrote:
> > > I wonder what happens if you echo 0 to /sys/power/pm_async ?
> >
> > Nothing happens. The problem persists (tested with 2.6.36-rc7). What
> > would you expect to happen?
>
> Exactly that. :-)
>
> Commit 152e1d5920 should not affect the non-async case (I'd be surprised if
> it did really) and things should work with /sys/power/pm_async = 0 anyway.
>
> Please try check if you can reproduce with commt 152e1d5920 reverted and
> /sys/power/pm_async = 0. If you can, that's a driver bug.
Ok, for the record, here's what I tried. I have rebooted between tests
to make sure there's no state pulled in from the previous test:
2.6.36-rc7, no changes, pm_async 1 : suspend fails
2.6.36-rc7, no changes, pm_async 0 : suspend fails
2.6.36-rc7, 152e1d reverted, pm_async 1 : suspend works
2.6.36-rc7, 152e1d reverted, pm_async 0 : suspend fails
2.6.34.7, no changes, pm_async 1 : suspend works
2.6.34.7, no changes, pm_async 0 : suspend works
I am not sure how this should be interpreted.
Sven
WARNING: multiple messages have this Message-ID (diff)
From: s.neumann@raumfeld.com (Sven Neumann)
To: linux-arm-kernel@lists.infradead.org
Subject: 2.6.35.6 fails to suspend (pxa2xx-mci.0)
Date: Fri, 08 Oct 2010 10:23:17 +0200 [thread overview]
Message-ID: <1286526197.4493.19.camel@sven> (raw)
In-Reply-To: <201010072323.05218.rjw@sisk.pl>
On Thu, 2010-10-07 at 23:23 +0200, Rafael J. Wysocki wrote:
> > > I wonder what happens if you echo 0 to /sys/power/pm_async ?
> >
> > Nothing happens. The problem persists (tested with 2.6.36-rc7). What
> > would you expect to happen?
>
> Exactly that. :-)
>
> Commit 152e1d5920 should not affect the non-async case (I'd be surprised if
> it did really) and things should work with /sys/power/pm_async = 0 anyway.
>
> Please try check if you can reproduce with commt 152e1d5920 reverted and
> /sys/power/pm_async = 0. If you can, that's a driver bug.
Ok, for the record, here's what I tried. I have rebooted between tests
to make sure there's no state pulled in from the previous test:
2.6.36-rc7, no changes, pm_async 1 : suspend fails
2.6.36-rc7, no changes, pm_async 0 : suspend fails
2.6.36-rc7, 152e1d reverted, pm_async 1 : suspend works
2.6.36-rc7, 152e1d reverted, pm_async 0 : suspend fails
2.6.34.7, no changes, pm_async 1 : suspend works
2.6.34.7, no changes, pm_async 0 : suspend works
I am not sure how this should be interpreted.
Sven
next prev parent reply other threads:[~2010-10-08 8:23 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 7:30 2.6.35.6 fails to suspend (pxa2xx-mci.0) Sven Neumann
2010-10-04 7:30 ` Sven Neumann
2010-10-04 7:48 ` Eric Miao
2010-10-04 7:48 ` Eric Miao
2010-10-06 18:59 ` Maciej Rutecki
2010-10-06 18:59 ` Maciej Rutecki
2010-10-06 23:55 ` Daniel Mack
2010-10-06 23:55 ` Daniel Mack
2010-10-07 0:18 ` Rafael J. Wysocki
2010-10-07 0:18 ` Rafael J. Wysocki
2010-10-07 15:03 ` Sven Neumann
2010-10-07 15:03 ` Sven Neumann
2010-10-07 21:23 ` Rafael J. Wysocki
2010-10-07 21:23 ` Rafael J. Wysocki
2010-10-08 8:23 ` Sven Neumann [this message]
2010-10-08 8:23 ` Sven Neumann
2010-10-08 20:08 ` Rafael J. Wysocki
2010-10-08 20:08 ` Rafael J. Wysocki
2010-10-09 1:07 ` Ohad Ben-Cohen
2010-10-09 1:07 ` Ohad Ben-Cohen
2010-10-09 23:20 ` Sven Neumann
2010-10-09 23:20 ` Sven Neumann
2010-10-11 8:31 ` Sven Neumann
2010-10-11 8:31 ` Sven Neumann
2010-10-11 8:45 ` Ohad Ben-Cohen
2010-10-11 8:45 ` Ohad Ben-Cohen
2010-10-11 9:11 ` Sven Neumann
2010-10-11 9:11 ` Sven Neumann
2010-10-13 7:31 ` [PATCH] sdio: fix suspend/resume regression Ohad Ben-Cohen
2010-10-13 7:31 ` Ohad Ben-Cohen
2010-10-13 7:31 ` Ohad Ben-Cohen
2010-10-13 7:54 ` Vitaly Wool
2010-10-13 7:54 ` Vitaly Wool
2010-10-13 8:55 ` Ohad Ben-Cohen
2010-10-13 8:55 ` Ohad Ben-Cohen
2010-10-13 9:06 ` Vitaly Wool
2010-10-13 9:06 ` Vitaly Wool
2010-10-13 9:46 ` Ohad Ben-Cohen
2010-10-13 9:46 ` Ohad Ben-Cohen
2010-10-13 20:00 ` Nicolas Pitre
2010-10-13 20:00 ` Nicolas Pitre
2010-10-13 20:08 ` Nicolas Pitre
2010-10-13 20:08 ` Nicolas Pitre
2010-10-14 15:28 ` Ohad Ben-Cohen
2010-10-14 15:28 ` Ohad Ben-Cohen
2010-10-14 2:24 ` Chris Ball
2010-10-14 2:24 ` Chris Ball
2010-10-14 4:49 ` Ohad Ben-Cohen
2010-10-14 4:49 ` Ohad Ben-Cohen
2010-10-21 23:47 ` Maxim Levitsky
2010-10-21 23:47 ` Maxim Levitsky
2010-10-21 23:55 ` Nicolas Pitre
2010-10-21 23:55 ` Nicolas Pitre
2010-10-22 0:25 ` Maxim Levitsky
2010-10-22 0:25 ` Maxim Levitsky
2010-10-21 23:57 ` Nicolas Pitre
2010-10-21 23:57 ` Nicolas Pitre
2010-10-23 10:09 ` Ohad Ben-Cohen
2010-10-23 10:09 ` Ohad Ben-Cohen
2010-10-23 14:18 ` Maxim Levitsky
2010-10-23 14:18 ` Maxim Levitsky
2010-10-23 14:44 ` Ohad Ben-Cohen
2010-10-23 14:44 ` Ohad Ben-Cohen
2010-10-11 8:10 ` 2.6.35.6 fails to suspend (pxa2xx-mci.0) Sven Neumann
2010-10-11 8:10 ` Sven Neumann
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=1286526197.4493.19.camel@sven \
--to=s.neumann@raumfeld.com \
--cc=ccross@android.com \
--cc=daniel@caiaq.de \
--cc=gregkh@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.