From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brad Campbell Subject: Re: Linux 3.0-rc4 intermittent failure to resume Date: Tue, 28 Jun 2011 10:39:09 +0800 Message-ID: <4E093ECD.7040600@fnarfbargle.com> References: <4E0286F3.6030003@wasp.net.au> <201106231402.59491.rjw@sisk.pl> <4E03F95B.9030101@fnarfbargle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4E03F95B.9030101@fnarfbargle.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: linux-pm@lists.linux-foundation.org List-Id: linux-pm@vger.kernel.org On 24/06/11 10:41, Brad Campbell wrote: > On 23/06/11 20:02, Rafael J. Wysocki wrote: >> On Thursday, June 23, 2011, Brad Campbell wrote: >>> G'day all, >>> >>> I've recently moved from tuxonice to mainline uswsusp. I'm getting intermittent failure to resume >>> problems. No message in dmesg that I can find, it just boots clean. Is there something I can do to >>> get some debug info on this? It's really, really annoying. >>> >>> About 75% of the time it works perfectly, and I can find no rhyme or reason to why it suddenly just >>> decides to ignore the saved state. >>> >>> 32 bit userspace with a statically linked 64 bit s2disk, s2both& resume. 64 bit kernel. >> Do you use the i915 driver? >> > Indeed I do. Just a follow up to this. It looks like adding "early writeout = y" to my /etc/suspend.conf has worked around the problem. If I had "shutdown method = reboot", then it would resume every time, but with "shutdown method = platform" it would fail to resume most of the time. I'm running a Core 2 Duo with an Intel X18-M 160GB SSD on an intel AHCI controller. Adding "early writeout = y" does not appear to change the progress statistics, or apparent speed of the suspend, but it has now survived 7 suspend/power off/resume cycles that it would never had survived before. Odd ??