public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Campbell <lists2009@fnarfbargle.com>
To: linux-pm@lists.linux-foundation.org
Subject: Re: Linux 3.0-rc4 intermittent failure to resume
Date: Wed, 29 Jun 2011 21:23:03 +0800	[thread overview]
Message-ID: <4E0B2737.2010505@fnarfbargle.com> (raw)
In-Reply-To: <4E093ECD.7040600@fnarfbargle.com>

On 28/06/11 10:39, Brad Campbell wrote:
> 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.
>

Ok, so after _lots_ of investigating it was not early writeout. The 
culprit was/is the Ubuntu initramfs scripts.

On the occasions it failed to resume (which were many) it turns out 
/bin/resume was being called prior to udev having created /dev/snapshot.

I put a simple wait loop in the resume script to wait for the creation 
of /dev/snapshot and I've not had a fail to resume since.

Curse you asynchronous dynamic device creation <shakes fist>

Regards,
Brad

  parent reply	other threads:[~2011-06-29 13:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23  0:21 Linux 3.0-rc4 intermittent failure to resume Brad Campbell
2011-06-23 12:02 ` Rafael J. Wysocki
2011-06-24  2:41   ` Brad Campbell
2011-06-28  2:39     ` Brad Campbell
2011-06-29  5:34       ` Brad Campbell
2011-06-29 13:23       ` Brad Campbell [this message]
2011-06-29 19:34         ` Rafael J. Wysocki
2011-06-30  0:21           ` Brad Campbell

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=4E0B2737.2010505@fnarfbargle.com \
    --to=lists2009@fnarfbargle.com \
    --cc=linux-pm@lists.linux-foundation.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