public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: suspend/resume fails on second attempt in LNXVIDEO:00
Date: Tue, 16 Dec 2008 17:22:40 +0100	[thread overview]
Message-ID: <200812161722.41149.rjw@sisk.pl> (raw)
In-Reply-To: <gi8kc5$m5f$6@ger.gmane.org>

On Tuesday, 16 of December 2008, Brian J. Murrell wrote:
> On Tue, 16 Dec 2008 17:13:08 +0100, Rafael J. Wysocki wrote:
> > 
> > Hm, this really isn't reasonable.
> 
> Many people agree with you.  :-)  There is a long bug open with ubuntu to 
> restore this s2ram.  They seem to be ignoring it though.
> 
> > s2both saves the image, which takes
> > quite a lot of time, while s2ram doesn't.
> 
> Indeed.
>  
> > You can compile s2ram from sources, it's not too difficult.
> 
> Yeah.  I will probably just grab the debian package and dpkg-buildpackage 
> it on my Ubuntu system.
>  
> > Hm.  Is that all loaded when you boot with init=/bin/bash (by which I
> > mean the minimal config)?
> 
> It sure is.  Most assuredly by the initrd.  Debian/Ubuntu systems seem to 
> put everything but the kitchen sink into their initrds.  Which on the one 
> hand makes them pretty portable and resilient, but on the other, yes, 
> bloated.

Well, please remove as many modules as you can (using rmmod) and see if your
second resume still fails.

Thanks,
Rafael

  reply	other threads:[~2008-12-16 16:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gi247o$iog$1@ger.gmane.org>
     [not found] ` <20081215155655.GA1535@ucw.cz>
2008-12-15 17:00   ` suspend/resume fails on second attempt in LNXVIDEO: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 [this message]
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
2008-12-19 21:10                     ` Brian J. Murrell
2008-12-20 17:43     ` Sergio Monteiro Basto
2008-12-20 21:08       ` 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=200812161722.41149.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox