From: Brad Campbell <lists2009@fnarfbargle.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: Linux 3.0-rc4 intermittent failure to resume
Date: Thu, 30 Jun 2011 08:21:44 +0800 [thread overview]
Message-ID: <4E0BC198.4040305@fnarfbargle.com> (raw)
In-Reply-To: <201106292134.34485.rjw@sisk.pl>
On 30/06/11 03:34, Rafael J. Wysocki wrote:
> On Wednesday, June 29, 2011, Brad Campbell wrote:
>> 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>
>
> Thank you very much for nailing this down, I was afraid there were some
> obscure bug lurking in the kernel code.
Yeah, no worries.
I set up a loop to do automated suspend/resume cycles.
I managed over 100 cycles while compiling 2 kernels in the background.
Over the 100 cycles the kernel locked up twice, but both times were in
very early boot. I power cycled the machine and it resumed with no
problems, so the issue is not with the suspend/resume code.
prev parent reply other threads:[~2011-06-30 0:21 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
2011-06-29 19:34 ` Rafael J. Wysocki
2011-06-30 0:21 ` Brad Campbell [this message]
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=4E0BC198.4040305@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=linux-pm@lists.linux-foundation.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.