[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1286526197.4493.19.camel@sven>
Date: Fri, 08 Oct 2010 10:23:17 +0200
From: Sven Neumann <s.neumann@...mfeld.com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Daniel Mack <daniel@...aq.de>, Colin Cross <ccross@...roid.com>,
Greg Kroah-Hartman <gregkh@...e.de>, linux-mmc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: 2.6.35.6 fails to suspend (pxa2xx-mci.0)
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
--
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