All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: suspend/resume fails on second attempt in LNXVIDEO:00
Date: Fri, 19 Dec 2008 18:33:10 +0100	[thread overview]
Message-ID: <200812191833.10979.rjw@sisk.pl> (raw)
In-Reply-To: <gieo1h$u78$1@ger.gmane.org>

On Friday, 19 of December 2008, Brian J. Murrell wrote:
> On Thu, 18 Dec 2008 04:24:44 +0000, Brian J. Murrell wrote:
> 
> > 
> > OK.  I've done my s2ram experiments and go no better than with pm-utils/
> > kernel mode suspend (where first suspend/resume works, second suspend
> > works, but second resume hangs the machine).  Here's the full array of
> > suggestions on http://en.opensuse.org/S2ram and their results:
> 
> Just wondering if any of this experimentation is likely to help me or is 
> this just a loser of a laptop that will be more trouble that it's worth 
> trying to get to suspend?  I can take it back to the store still.  Maybe 
> I should and try a different one?
> 
> Or does it seem like there still might be a relatively easy fix for this 
> problem, which would be nice given that it was a pretty good deal (or was 
> it?).  :-)

You're not the only person having a problem like this and unfortunately it's
not easy to debug.  I don't know of any fixes available.

Thanks,
Rafael

  reply	other threads:[~2008-12-19 17:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-14  5:06 suspend/resume fails on second attempt in LNXVIDEO:00 Brian J. Murrell
2008-12-14  6:43 ` Justin P. Mattock
2008-12-14 20:55   ` Brian J. Murrell
2008-12-14 22:29     ` Justin P. Mattock
2008-12-15 15:56 ` Pavel Machek
2008-12-15 17:00   ` Brian J. Murrell
2008-12-15 17:33     ` Alexey Starikovskiy
2008-12-15 17:56       ` Brian J. Murrell
2008-12-15 20:19         ` Rafael J. Wysocki
2008-12-15 20:52           ` Brian J. Murrell
2008-12-15 23:02             ` Rafael J. Wysocki
2008-12-16  2:34               ` Brian J. Murrell
2008-12-16 15:25                 ` Rafael J. Wysocki
2008-12-16 16:02                   ` Brian J. Murrell
2008-12-16 16:13                     ` Rafael J. Wysocki
2008-12-16 16:18                       ` Brian J. Murrell
2008-12-16 16:22                         ` Rafael J. Wysocki
2008-12-16 23:54                           ` Brian J. Murrell
2008-12-16 16:37                       ` Matthew Garrett
2008-12-16 18:07                         ` Brian J. Murrell
2008-12-16 20:53                           ` Matthew Garrett
2008-12-18  7:52                             ` Pavel Machek
2008-12-18  8:11                               ` Justin P. Mattock
2008-12-18  4:24               ` Brian J. Murrell
2008-12-18 23:57                 ` Brian J. Murrell
2008-12-19 17:33                   ` Rafael J. Wysocki [this message]
2008-12-19 21:10                     ` Brian J. Murrell
2008-12-20 17:43     ` Sergio Monteiro Basto
2008-12-20 21:08       ` Brian J. Murrell
  -- strict thread matches above, loose matches on Subject: below --
2008-12-14  9:16 Robby Workman
2008-12-14 14:08 ` Brian J. Murrell
2008-12-14 15:35   ` Justin P. Mattock
2008-12-14 17:06     ` Brian J. Murrell

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=200812191833.10979.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=brian@interlinx.bc.ca \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 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.