public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Brian J. Murrell" <brian@interlinx.bc.ca>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: suspend/resume fails on second attempt in LNXVIDEO:00
Date: Thu, 18 Dec 2008 08:52:27 +0100	[thread overview]
Message-ID: <20081218075226.GD2110@ucw.cz> (raw)
In-Reply-To: <20081216205335.GA14332@srcf.ucam.org>

On Tue 2008-12-16 20:53:35, Matthew Garrett wrote:
> On Tue, Dec 16, 2008 at 06:07:15PM +0000, Brian J. Murrell wrote:
> > On Tue, 16 Dec 2008 16:37:46 +0000, Matthew Garrett wrote:
> > > 
> > > I seem to be missing the original message, but: no, s2ram doesn't exist
> > > in Ubuntu because pm-utils handles that role.
> > 
> > Well, that's *their* argument but lots of people think otherwise.  There 
> > appears to be no shortage of people for whom pm-utils does NOT work yet 
> > s2ram does.  https://bugs.launchpad.net/ubuntu/+source/uswsusp/+bug/134238
> 
> The right answer to "This piece of software contains bugs" is not 
> "Provide two pieces of software with the same features but different 
> bugs". The only real functional difference between the two is that

Yes, and that's why pm-utils should die: they have design problems
(depend on hal, can't be pagelocked, unusable for suspend debugging).
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-12-18  7:52 UTC|newest]

Thread overview: 24+ 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
     [not found]       ` <gi65ol$bnf$7@ger.gmane.org>
2008-12-15 20:19         ` Rafael J. Wysocki
     [not found]           ` <gi6g21$bnf$8@ger.gmane.org>
2008-12-15 23:02             ` Rafael J. Wysocki
     [not found]               ` <gi7433$m5f$1@ger.gmane.org>
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 16:37                       ` Matthew Garrett
     [not found]                         ` <gi8qoj$m5f$7@ger.gmane.org>
2008-12-16 20:53                           ` Matthew Garrett
2008-12-18  7:52                             ` Pavel Machek [this message]
2008-12-18  8:11                               ` Justin P. Mattock
2008-12-20 17:43     ` Sergio Monteiro Basto
     [not found] ` <gicjac$m5f$11@ger.gmane.org>
     [not found]   ` <gieo1h$u78$1@ger.gmane.org>
2008-12-19 17:33     ` Rafael J. Wysocki
  -- 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=20081218075226.GD2110@ucw.cz \
    --to=pavel@suse.cz \
    --cc=brian@interlinx.bc.ca \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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