From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: 2.6.35.6 fails to suspend (pxa2xx-mci.0) Date: Thu, 7 Oct 2010 02:18:41 +0200 Message-ID: <201010070218.41944.rjw@sisk.pl> References: <1286177435.2140.5.camel@sven> <20101006235513.GY7159@buzzloop.caiaq.de> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from ogre.sisk.pl ([217.79.144.158]:51700 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753566Ab0JGAT0 (ORCPT ); Wed, 6 Oct 2010 20:19:26 -0400 In-Reply-To: <20101006235513.GY7159@buzzloop.caiaq.de> Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Daniel Mack Cc: Colin Cross , Greg Kroah-Hartman , Sven Neumann , linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org On Thursday, October 07, 2010, Daniel Mack wrote: > On Mon, Oct 04, 2010 at 09:30:35AM +0200, Sven Neumann wrote: > > we are running an embedded system here based on the PXA300 platform. > > Suspend/resume used to work well so far. However after upgrading the > > kernel from 2.6.34.7 to 2.6.35.6, we get the following error when trying > > to suspend the system: > > > > # echo "mem" > "/sys/power/state" > > [ 5647.295953] PM: Syncing filesystems ... done. > > [ 5647.318792] Freezing user space processes ... (elapsed 0.01 seconds) done. > > [ 5647.337048] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. > > [ 5647.356915] Suspending console(s) (use no_console_suspend to debug) > > [ 5647.366651] pm_op(): platform_pm_suspend+0x0/0x5c returns -38 > > [ 5647.366671] PM: Device pxa2xx-mci.0 failed to suspend: error -38 > > [ 5647.367082] PM: Some devices failed to suspend > > We've bisected this effect down to commit 152e1d5920 ("PM: Prevent > waiting forever on asynchronous resume after failing suspend"). > Suspending our PXA3xx based system breaks with this patch. > > I tried to understand what's going wrong, but I didn't follow the > discussion about this logic, so I would rather like to pass it back to > the originating people. > > I can only guess that the problem here is the somewhat tricky handling > around mmc_sdio_suspend(), which returns -ENODEV (-38) in case a > particular function of a card can not be suspended. The SDIO core would > have simply removed the card in this case normally, but the PM core > seems to interfere now, stopping the whole suspend procedure. > > Can anyone shed some light on this? I wonder what happens if you echo 0 to /sys/power/pm_async ? Rafael